Encoder, decoder and corresponding methods for simplifying signalling picture header

ABSTRACT

A method of coding implemented by a decoding device is provided. The method includes parsing a bitstream to obtain a flag from a picture header of the bitstream, wherein the flag indicates whether a current picture is I picture. when the flag indicates that the current picture is I picture, a syntax element designed for inter prediction is inferred to a default value; or when the flag indicates that the current picture is P or B picture, obtaining a syntax element designed for inter prediction from the picture header.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No. PCT/CN2020/120110, filed on Oct. 10, 2020, which claims priority to U.S. provisional Application No. 62/913,730, filed on Oct. 10, 2019. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties.

TECHNICAL FIELD

Embodiments of the present application (disclosure) generally relate to the field of picture processing and more particularly to simplify signaling picture header.

BACKGROUND

Video coding (video encoding and decoding) is used in a wide range of digital video applications, for example broadcast digital TV, video transmission over internet and mobile networks, real-time conversational applications such as video chat, video conferencing, DVD and Blu-ray discs, video content acquisition and editing systems, and camcorders of security applications.

The amount of video data needed to depict even a relatively short video can be substantial, which may result in difficulties when the data is to be streamed or otherwise communicated across a communications network with limited bandwidth capacity. Thus, video data is generally compressed before being communicated across modern day telecommunications networks. The size of a video could also be an issue when the video is stored on a storage device because memory resources may be limited. Video compression devices often use software and/or hardware at the source to code the video data prior to transmission or storage, thereby decreasing the quantity of data needed to represent digital video images. The compressed data is then received at the destination by a video decompression device that decodes the video data. With limited network resources and ever increasing demands of higher video quality, simplifying signaling picture header is desirable.

SUMMARY

Embodiments of the present application provide apparatuses and methods for encoding and decoding according to the independent claims.

The foregoing and other objects are achieved by the subject matter of the independent claims. Further implementation forms are apparent from the dependent claims, the description and the figures.

According to a first aspect, a method of coding implemented by a decoding device, includes parsing a bitstream to obtain a flag from a picture header of the bitstream, wherein the flag indicates whether a current picture is I picture.

When the flag indicates that the current picture is I picture, a syntax element designed for inter prediction is inferred to a default value; or when the flag indicates that the current picture is P or B picture, obtaining a syntax element designed for inter prediction from the picture header.

The syntax element designed for inter prediction includes one or more of the following elements: pic_log2_diff_min_qt_min_cb_inter_slice, pic_max_mtt_hierarchy_depth_inter_slice, pic_log2_diff_max_bt_min_qt_inter_slice, pic_log2_diff_max_tt_min_qt_inter_slice, pic_cu_qp_delta_subdiv_inter_slice, pic_cu_chroma_qp_offset_subdiv_inter_slice, pic_temporal_mvp_enabled_flag, mvd_l1_zero_flag, pic_fpel_mmvd_enabled_flag, or pic_disable_bdof_dmvr_flag.

According to a second aspect, a method of coding implemented by an encoding device, includes determining whether a current picture is I picture; and

sending a bitstream to a decoding device, wherein a picture header of the bitstream includes a flag indicating whether the current picture is I picture; and wherein when the current picture is I picture, a syntax element designed for inter prediction is not signaled in the picture header; or when the current picture is P or B picture, a syntax element designed for inter prediction is signaled in the picture header.

The method according to the first aspect of the specification can be performed by the apparatus according to a third aspect of the specification. Further features and implementation forms of the method according to the third aspect of the specification correspond to the features and implementation forms of the apparatus according to the first aspect of the specification.

The method according to the second aspect of the specification can be performed by the apparatus according to a fourth aspect of the specification. Further features and implementation forms of the method according to the fourth aspect of the specification correspond to the features and implementation forms of the apparatus according to the second aspect of the specification.

According to a fifth aspect, an apparatus for decoding a video stream includes a processor and a memory. The memory is storing instructions that cause the processor to perform the method according to the first aspect.

According to a sixth aspect, an apparatus for encoding a video stream includes a processor and a memory. The memory is storing instructions that cause the processor to perform the method according to the second aspect.

According to a seventh aspect, a computer-readable storage medium having stored thereon instructions that when executed cause one or more processors configured to code video data is proposed. The instructions cause the one or more processors to perform a method according to the first or second aspect or any possible embodiment of the first or second aspect.

According to an eighth aspect, a computer program comprising program code for performing the method according to the first or second aspect or any possible embodiment of the first or second aspect when executed on a computer.

As discussed above, by indicating whether the current picture is I picture in the picture header of the bitstream, the syntax element designed for inter prediction is not signaled in the picture header when the current picture is I picture. Thus, the embodiments can simplify signaling picture header for all intra pictures, i.e., I picture. Correspondingly, signaling overhead is reduced.

Details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description, drawings, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following embodiments of the specification are described in more detail with reference to the attached figures and drawings, in which:

FIG. 1A is a block diagram showing an example of a video coding system configured to implement embodiments of the specification;

FIG. 1B is a block diagram showing another example of a video coding system configured to implement embodiments of the specification;

FIG. 2 is a block diagram showing an example of a video encoder configured to implement embodiments of the specification;

FIG. 3 is a block diagram showing an example structure of a video decoder configured to implement embodiments of the specification;

FIG. 4 is a block diagram illustrating an example of an encoding apparatus or a decoding apparatus;

FIG. 5 is a block diagram illustrating another example of an encoding apparatus or a decoding apparatus;

FIG. 6 is an example of picture parameter set RBSP syntax;

FIG. 7 is an example of picture parameter set RBSP syntax;

FIG. 8 is an example of an adaptation parameter set syntax;

FIG. 9 is an example of General slice header syntax;

FIG. 10a is an example of the coding tree unit syntax structure;

FIG. 11 is another example of General slice header syntax;

FIG. 12 shows a flow chart 1200 illustrating a method implemented by an encoding device according to an embodiment;

FIG. 13 shows a flow chart 1300 illustrating a method implemented by a decoding device according to an embodiment;

FIG. 14 illustrates a configuration of an encoding device;

FIG. 15 illustrates a configuration of a decoding device;

FIG. 16 is a block diagram showing an example structure of a content supply system 3100 which realizes a content delivery service; and

FIG. 17 is a block diagram showing a structure of an example of a terminal device.

In the following identical reference signs refer to identical or at least functionally equivalent features if not explicitly specified otherwise.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In the following description, reference is made to the accompanying figures, which form part of the disclosure, and which show, by way of illustration, specific aspects of embodiments of the specification or specific aspects in which embodiments of the present specification may be used. It is understood that embodiments of the specification may be used in other aspects and comprise structural or logical changes not depicted in the figures. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present specification is defined by the appended claims.

For instance, it is understood that a disclosure in connection with a described method may also hold true for a corresponding device or system configured to perform the method and vice versa. For example, if one or a plurality of specific method steps are described, a corresponding device may include one or a plurality of units, e.g. functional units, to perform the described one or plurality of method steps (e.g. one unit performing the one or plurality of steps, or a plurality of units each performing one or more of the plurality of steps), even if such one or more units are not explicitly described or illustrated in the figures. On the other hand, for example, if a specific apparatus is described based on one or a plurality of units, e.g. functional units, a corresponding method may include one step to perform the functionality of the one or plurality of units (e.g. one step performing the functionality of the one or plurality of units, or a plurality of steps each performing the functionality of one or more of the plurality of units), even if such one or plurality of steps are not explicitly described or illustrated in the figures. Further, it is understood that the features of the various exemplary embodiments and/or aspects described herein may be combined with each other, unless specifically noted otherwise.

Video coding typically refers to the processing of a sequence of pictures, which form the video or video sequence. Instead of the term “picture” the term “frame” or “image” may be used as synonyms in the field of video coding. Video coding (or coding in general) comprises two parts video encoding and video decoding. Video encoding is performed at the source side, typically comprising processing (e.g. by compression) the original video pictures to reduce the amount of data required for representing the video pictures (for more efficient storage and/or transmission). Video decoding is performed at the destination side and typically comprises the inverse processing compared to the encoder to reconstruct the video pictures. Embodiments referring to “coding” of video pictures (or pictures in general) shall be understood to relate to “encoding” or “decoding” of video pictures or respective video sequences. The combination of the encoding part and the decoding part is also referred to as CODEC (Coding and Decoding).

In case of lossless video coding, the original video pictures can be reconstructed, i.e. the reconstructed video pictures have the same quality as the original video pictures (assuming no transmission loss or other data loss during storage or transmission). In case of lossy video coding, further compression, e.g. by quantization, is performed, to reduce the amount of data representing the video pictures, which cannot be completely reconstructed at the decoder, i.e. the quality of the reconstructed video pictures is lower or worse compared to the quality of the original video pictures.

Several video coding standards belong to the group of “lossy hybrid video codecs” (i.e. combine spatial and temporal prediction in the sample domain and 2D transform coding for applying quantization in the transform domain). Each picture of a video sequence is typically partitioned into a set of non-overlapping blocks and the coding is typically performed on a block level. In other words, at the encoder the video is typically processed, i.e. encoded, on a block (video block) level, e.g. by using spatial (intra picture) prediction and/or temporal (inter picture) prediction to generate a prediction block, subtracting the prediction block from the current block (block currently processed/to be processed) to obtain a residual block, transforming the residual block and quantizing the residual block in the transform domain to reduce the amount of data to be transmitted (compression), whereas at the decoder the inverse processing compared to the encoder is applied to the encoded or compressed block to reconstruct the current block for representation. Furthermore, the encoder duplicates the decoder processing loop such that both will generate identical predictions (e.g. intra- and inter predictions) and/or re-constructions for processing, i.e. coding, the subsequent blocks.

In the following embodiments of a video coding system 10, a video encoder 20 and a video decoder 30 are described based on FIGS. 1 to 3.

FIG. 1A is a schematic block diagram illustrating an example coding system 10, e.g. a video coding system 10 (or short coding system 10) that may utilize techniques of this present application. Video encoder 20 (or short encoder 20) and video decoder 30 (or short decoder 30) of video coding system 10 represent examples of devices that may be configured to perform techniques in accordance with various examples described in the present application.

As shown in FIG. 1A, the coding system 10 comprises a source device 12 configured to provide encoded picture data 21 e.g. to a destination device 14 for decoding the encoded picture data 13.

The source device 12 comprises an encoder 20, and may additionally, i.e. optionally, comprise a picture source 16, a pre-processor (or pre-processing unit) 18, e.g. a picture pre-processor 18, and a communication interface or communication unit 22.

The picture source 16 may comprise or be any kind of picture capturing device, for example a camera for capturing a real-world picture, and/or any kind of a picture generating device, for example a computer-graphics processor for generating a computer animated picture, or any kind of other device for obtaining and/or providing a real-world picture, a computer generated picture (e.g. a screen content, a virtual reality (VR) picture) and/or any combination thereof (e.g. an augmented reality (AR) picture). The picture source may be any kind of memory or storage storing any of the aforementioned pictures.

In distinction to the pre-processor 18 and the processing performed by the pre-processing unit 18, the picture or picture data 17 may also be referred to as raw picture or raw picture data 17.

Pre-processor 18 is configured to receive the (raw) picture data 17 and to perform pre-processing on the picture data 17 to obtain a pre-processed picture 19 or pre-processed picture data 19. Pre-processing performed by the pre-processor 18 may, e.g., comprise trimming, color format conversion (e.g. from RGB to YCbCr), color correction, or de-noising. It can be understood that the pre-processing unit 18 may be optional component.

The video encoder 20 is configured to receive the pre-processed picture data 19 and provide encoded picture data 21 (further details will be described below, e.g., based on FIG. 2).

Communication interface 22 of the source device 12 may be configured to receive the encoded picture data 21 and to transmit the encoded picture data 21 (or any further processed version thereof) over communication channel 13 to another device, e.g. the destination device 14 or any other device, for storage or direct reconstruction.

The destination device 14 comprises a decoder 30 (e.g. a video decoder 30), and may additionally, i.e. optionally, comprise a communication interface or communication unit 28, a post-processor 32 (or post-processing unit 32) and a display device 34.

The communication interface 28 of the destination device 14 is configured receive the encoded picture data 21 (or any further processed version thereof), e.g. directly from the source device 12 or from any other source, e.g. a storage device, e.g. an encoded picture data storage device, and provide the encoded picture data 21 to the decoder 30.

The communication interface 22 and the communication interface 28 may be configured to transmit or receive the encoded picture data 21 or encoded data 13 via a direct communication link between the source device 12 and the destination device 14, e.g. a direct wired or wireless connection, or via any kind of network, e.g. a wired or wireless network or any combination thereof, or any kind of private and public network, or any kind of combination thereof.

The communication interface 22 may be, e.g., configured to package the encoded picture data 21 into an appropriate format, e.g. packets, and/or process the encoded picture data using any kind of transmission encoding or processing for transmission over a communication link or communication network.

The communication interface 28, forming the counterpart of the communication interface 22, may be, e.g., configured to receive the transmitted data and process the transmission data using any kind of corresponding transmission decoding or processing and/or de-packaging to obtain the encoded picture data 21.

Both, communication interface 22 and communication interface 28 may be configured as unidirectional communication interfaces as indicated by the arrow for the communication channel 13 in FIG. 1A pointing from the source device 12 to the destination device 14, or bi-directional communication interfaces, and may be configured, e.g. to send and receive messages, e.g. to set up a connection, to acknowledge and exchange any other information related to the communication link and/or data transmission, e.g. encoded picture data transmission.

The decoder 30 is configured to receive the encoded picture data 21 and provide decoded picture data 31 or a decoded picture 31 (further details will be described below, e.g., based on FIG. 3 or FIG. 5).

The post-processor 32 of destination device 14 is configured to post-process the decoded picture data 31 (also called reconstructed picture data), e.g. the decoded picture 31, to obtain post-processed picture data 33, e.g. a post-processed picture 33. The post-processing performed by the post-processing unit 32 may comprise, e.g. color format conversion (e.g. from YCbCr to RGB), color correction, trimming, or re-sampling, or any other processing, e.g. for preparing the decoded picture data 31 for display, e.g. by display device 34.

The display device 34 of the destination device 14 is configured to receive the post-processed picture data 33 for displaying the picture, e.g. to a user or viewer. The display device 34 may be or comprise any kind of display for representing the reconstructed picture, e.g. an integrated or external display or monitor. The displays may, e.g. comprise liquid crystal displays (LCD), organic light emitting diodes (OLED) displays, plasma displays, projectors, micro LED displays, liquid crystal on silicon (LCoS), digital light processor (DLP) or any kind of other display.

Although FIG. 1A depicts the source device 12 and the destination device 14 as separate devices, embodiments of devices may also comprise both or both functionalities, the source device 12 or corresponding functionality and the destination device 14 or corresponding functionality. In such embodiments the source device 12 or corresponding functionality and the destination device 14 or corresponding functionality may be implemented using the same hardware and/or software or by separate hardware and/or software or any combination thereof.

As will be apparent for the skilled person based on the description, the existence and (exact) split of functionalities of the different units or functionalities within the source device 12 and/or destination device 14 as shown in FIG. 1A may vary depending on the actual device and application.

The encoder 20 (e.g. a video encoder 20) or the decoder 30 (e.g. a video decoder 30) or both encoder 20 and decoder 30 may be implemented via processing circuitry as shown in FIG. 1B, such as one or more microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), discrete logic, hardware, video coding dedicated or any combinations thereof. The encoder 20 may be implemented via processing circuitry 46 to embody the various modules as discussed with respect to encoder 20 of FIG. 2 and/or any other encoder system or subsystem described herein. The decoder 30 may be implemented via processing circuitry 46 to embody the various modules as discussed with respect to decoder 30 of FIG. 3 and/or any other decoder system or subsystem described herein. The processing circuitry may be configured to perform the various operations as discussed later. As shown in FIG. 5, if the techniques are implemented partially in software, a device may store instructions for the software in a suitable, non-transitory computer-readable storage medium and may execute the instructions in hardware using one or more processors to perform the techniques of this disclosure. Either of video encoder 20 and video decoder 30 may be integrated as part of a combined encoder/decoder (CODEC) in a single device, for example, as shown in FIG. 1B.

Source device 12 and destination device 14 may comprise any of a wide range of devices, including any kind of handheld or stationary devices, e.g. notebook or laptop computers, mobile phones, smart phones, tablets or tablet computers, cameras, desktop computers, set-top boxes, televisions, display devices, digital media players, video gaming consoles, video streaming devices (such as content services servers or content delivery servers), broadcast receiver device, broadcast transmitter device, or the like and may use no or any kind of operating system. In some cases, the source device 12 and the destination device 14 may be equipped for wireless communication. Thus, the source device 12 and the destination device 14 may be wireless communication devices.

In some cases, video coding system 10 illustrated in FIG. 1A is merely an example and the techniques of the present application may apply to video coding settings (e.g., video encoding or video decoding) that do not necessarily include any data communication between the encoding and decoding devices. In other examples, data is retrieved from a local memory, streamed over a network, or the like. A video encoding device may encode and store data to memory, and/or a video decoding device may retrieve and decode data from memory. In some examples, the encoding and decoding is performed by devices that do not communicate with one another, but simply encode data to memory and/or retrieve and decode data from memory.

For convenience of description, embodiments of the specification are described herein, for example, by reference to High-Efficiency Video Coding (HEVC) or to the reference software of Versatile Video coding (VVC), the next generation video coding standard developed by the Joint Collaboration Team on Video Coding (JCT-VC) of ITU-T Video Coding Experts Group (VCEG) and ISO/IEC Motion Picture Experts Group (MPEG). One of ordinary skill in the art will understand that embodiments of the specification are not limited to HEVC or VVC.

Encoder and Encoding Method

FIG. 2 shows a schematic block diagram of an example video encoder 20 that is configured to implement the techniques of the present application. In the example of FIG. 2, the video encoder 20 comprises an input 201 (or input interface 201), a residual calculation unit 204, a transform processing unit 206, a quantization unit 208, an inverse quantization unit 210, and inverse transform processing unit 212, a reconstruction unit 214, a loop filter unit 220, a decoded picture buffer (DPB) 230, a mode selection unit 260, an entropy encoding unit 270 and an output 272 (or output interface 272). The mode selection unit 260 may include an inter prediction unit 244, an intra prediction unit 254 and a partitioning unit 262. Inter prediction unit 244 may include a motion estimation unit and a motion compensation unit (not shown). A video encoder 20 as shown in FIG. 2 may also be referred to as hybrid video encoder or a video encoder according to a hybrid video codec.

The residual calculation unit 204, the transform processing unit 206, the quantization unit 208, the mode selection unit 260 may be referred to as forming a forward signal path of the encoder 20, whereas the inverse quantization unit 210, the inverse transform processing unit 212, the reconstruction unit 214, the buffer 216, the loop filter 220, the decoded picture buffer (DPB) 230, the inter prediction unit 244 and the intra-prediction unit 254 may be referred to as forming a backward signal path of the video encoder 20, wherein the backward signal path of the video encoder 20 corresponds to the signal path of the decoder (see video decoder 30 in FIG. 3). The inverse quantization unit 210, the inverse transform processing unit 212, the reconstruction unit 214, the loop filter 220, the decoded picture buffer (DPB) 230, the inter prediction unit 244 and the intra-prediction unit 254 are also referred to forming the “built-in decoder” of video encoder 20.

Pictures & Picture Partitioning (Pictures & Blocks)

The encoder 20 may be configured to receive, e.g. via input 201, a picture 17 (or picture data 17), e.g. picture of a sequence of pictures forming a video or video sequence. The received picture or picture data may also be a pre-processed picture 19 (or pre-processed picture data 19). For sake of simplicity the following description refers to the picture 17. The picture 17 may also be referred to as current picture or picture to be coded (in particular in video coding to distinguish the current picture from other pictures, e.g. previously encoded and/or decoded pictures of the same video sequence, i.e. the video sequence which also comprises the current picture).

A (digital) picture is or can be regarded as a two-dimensional array or matrix of samples with intensity values. A sample in the array may also be referred to as pixel (short form of picture element) or a pel. The number of samples in horizontal and vertical direction (or axis) of the array or picture define the size and/or resolution of the picture. For representation of color, typically three color components are employed, i.e. the picture may be represented or include three sample arrays. In RBG format or color space a picture comprises a corresponding red, green and blue sample array. However, in video coding each pixel is typically represented in a luminance and chrominance format or color space, e.g. YCbCr, which comprises a luminance component indicated by Y (sometimes also L is used instead) and two chrominance components indicated by Cb and Cr. The luminance (or short luma) component Y represents the brightness or grey level intensity (e.g. like in a grey-scale picture), while the two chrominance (or short chroma) components Cb and Cr represent the chromaticity or color information components. Accordingly, a picture in YCbCr format comprises a luminance sample array of luminance sample values (Y), and two chrominance sample arrays of chrominance values (Cb and Cr). Pictures in RGB format may be converted or transformed into YCbCr format and vice versa, the process is also known as color transformation or conversion. If a picture is monochrome, the picture may comprise only a luminance sample array. Accordingly, a picture may be, for example, an array of luma samples in monochrome format or an array of luma samples and two corresponding arrays of chroma samples in 4:2:0, 4:2:2, and 4:4:4 colour format.

Embodiments of the video encoder 20 may comprise a picture partitioning unit (not depicted in FIG. 2) configured to partition the picture 17 into a plurality of (typically non-overlapping) picture blocks 203. These blocks may also be referred to as root blocks, macro blocks (H.264/AVC) or coding tree blocks (CTB) or coding tree units (CTU) (H.265/HEVC and VVC). The picture partitioning unit may be configured to use the same block size for all pictures of a video sequence and the corresponding grid defining the block size, or to change the block size between pictures or subsets or groups of pictures, and partition each picture into the corresponding blocks.

In further embodiments, the video encoder may be configured to receive directly a block 203 of the picture 17, e.g. one, several or all blocks forming the picture 17. The picture block 203 may also be referred to as current picture block or picture block to be coded.

Like the picture 17, the picture block 203 again is or can be regarded as a two-dimensional array or matrix of samples with intensity values (sample values), although of smaller dimension than the picture 17. In other words, the block 203 may comprise, e.g., one sample array (e.g. a luma array in case of a monochrome picture 17, or a luma or chroma array in case of a color picture) or three sample arrays (e.g. a luma and two chroma arrays in case of a color picture 17) or any other number and/or kind of arrays depending on the color format applied. The number of samples in horizontal and vertical direction (or axis) of the block 203 define the size of block 203. Accordingly, a block may, for example, an M×N (M-column by N-row) array of samples, or an M×N array of transform coefficients.

Embodiments of the video encoder 20 as shown in FIG. 2 may be configured to encode the picture 17 block by block, e.g. the encoding and prediction is performed per block 203.

Embodiments of the video encoder 20 as shown in FIG. 2 may be further configured to partition and/or encode the picture by using slices (also referred to as video slices), wherein a picture may be partitioned into or encoded using one or more slices (typically non-overlapping), and each slice may comprise one or more blocks (e.g. CTUs).

Embodiments of the video encoder 20 as shown in FIG. 2 may be further configured to partition and/or encode the picture by using tile groups (also referred to as video tile groups) and/or tiles (also referred to as video tiles), wherein a picture may be partitioned into or encoded using one or more tile groups (typically non-overlapping), and each tile group may comprise, e.g. one or more blocks (e.g. CTUs) or one or more tiles, wherein each tile, e.g. may be of rectangular shape and may comprise one or more blocks (e.g. CTUs), e.g. complete or fractional blocks.

Residual Calculation

The residual calculation unit 204 may be configured to calculate a residual block 205 (also referred to as residual 205) based on the picture block 203 and a prediction block 265 (further details about the prediction block 265 are provided later), e.g. by subtracting sample values of the prediction block 265 from sample values of the picture block 203, sample by sample (pixel by pixel) to obtain the residual block 205 in the sample domain.

Transform

The transform processing unit 206 may be configured to apply a transform, e.g. a discrete cosine transform (DCT) or discrete sine transform (DST), on the sample values of the residual block 205 to obtain transform coefficients 207 in a transform domain. The transform coefficients 207 may also be referred to as transform residual coefficients and represent the residual block 205 in the transform domain.

The transform processing unit 206 may be configured to apply integer approximations of DCT/DST, such as the transforms specified for H.265/HEVC. Compared to an orthogonal DCT transform, such integer approximations are typically scaled by a certain factor. In order to preserve the norm of the residual block which is processed by forward and inverse transforms, additional scaling factors are applied as part of the transform process. The scaling factors are typically chosen based on certain constraints like scaling factors being a power of two for shift operations, bit depth of the transform coefficients, tradeoff between accuracy and implementation costs, etc. Specific scaling factors are, for example, specified for the inverse transform, e.g. by inverse transform processing unit 212 (and the corresponding inverse transform, e.g. by inverse transform processing unit 312 at video decoder 30) and corresponding scaling factors for the forward transform, e.g. by transform processing unit 206, at an encoder 20 may be specified accordingly.

Embodiments of the video encoder 20 (respectively transform processing unit 206) may be configured to output transform parameters, e.g. a type of transform or transforms, e.g. directly or encoded or compressed via the entropy encoding unit 270, so that, e.g., the video decoder 30 may receive and use the transform parameters for decoding.

Quantization

The quantization unit 208 may be configured to quantize the transform coefficients 207 to obtain quantized coefficients 209, e.g. by applying scalar quantization or vector quantization. The quantized coefficients 209 may also be referred to as quantized transform coefficients 209 or quantized residual coefficients 209.

The quantization process may reduce the bit depth associated with some or all of the transform coefficients 207. For example, an n-bit transform coefficient may be rounded down to an m-bit Transform coefficient during quantization, where n is greater than m. The degree of quantization may be modified by adjusting a quantization parameter (QP). For example for scalar quantization, different scaling may be applied to achieve finer or coarser quantization. Smaller quantization step sizes correspond to finer quantization, whereas larger quantization step sizes correspond to coarser quantization. The applicable quantization step size may be indicated by a quantization parameter (QP). The quantization parameter may for example be an index to a predefined set of applicable quantization step sizes. For example, small quantization parameters may correspond to fine quantization (small quantization step sizes) and large quantization parameters may correspond to coarse quantization (large quantization step sizes) or vice versa. The quantization may include division by a quantization step size and a corresponding and/or the inverse dequantization, e.g. by inverse quantization unit 210, may include multiplication by the quantization step size. Embodiments according to some standards, e.g. HEVC, may be configured to use a quantization parameter to determine the quantization step size. Generally, the quantization step size may be calculated based on a quantization parameter using a fixed point approximation of an equation including division. Additional scaling factors may be introduced for quantization and dequantization to restore the norm of the residual block, which might get modified because of the scaling used in the fixed point approximation of the equation for quantization step size and quantization parameter. In one example implementation, the scaling of the inverse transform and dequantization might be combined. Alternatively, customized quantization tables may be used and signaled from an encoder to a decoder, e.g. in a bitstream. The quantization is a lossy operation, wherein the loss increases with increasing quantization step sizes.

Embodiments of the video encoder 20 (respectively quantization unit 208) may be configured to output quantization parameters (QP), e.g. directly or encoded via the entropy encoding unit 270, so that, e.g., the video decoder 30 may receive and apply the quantization parameters for decoding.

Inverse Quantization

The inverse quantization unit 210 is configured to apply the inverse quantization of the quantization unit 208 on the quantized coefficients to obtain dequantized coefficients 211, e.g. by applying the inverse of the quantization scheme applied by the quantization unit 208 based on or using the same quantization step size as the quantization unit 208. The dequantized coefficients 211 may also be referred to as dequantized residual coefficients 211 and correspond—although typically not identical to the transform coefficients due to the loss by quantization—to the transform coefficients 207.

Inverse Transform

The inverse transform processing unit 212 is configured to apply the inverse transform of the transform applied by the transform processing unit 206, e.g. an inverse discrete cosine transform (DCT) or inverse discrete sine transform (DST) or other inverse transforms, to obtain a reconstructed residual block 213 (or corresponding dequantized coefficients 213) in the sample domain. The reconstructed residual block 213 may also be referred to as transform block 213.

Reconstruction

The reconstruction unit 214 (e.g. adder or summer 214) is configured to add the transform block 213 (i.e. reconstructed residual block 213) to the prediction block 265 to obtain a reconstructed block 215 in the sample domain, e.g. by adding—sample by sample—the sample values of the reconstructed residual block 213 and the sample values of the prediction block 265.

Filtering

The loop filter unit 220 (or short “loop filter” 220), is configured to filter the reconstructed block 215 to obtain a filtered block 221, or in general, to filter reconstructed samples to obtain filtered samples. The loop filter unit is, e.g., configured to smooth pixel transitions, or otherwise improve the video quality. The loop filter unit 220 may comprise one or more loop filters such as a de-blocking filter, a sample-adaptive offset (SAO) filter or one or more other filters, e.g. a bilateral filter, an adaptive loop filter (ALF), a sharpening, a smoothing filters or a collaborative filters, or any combination thereof. Although the loop filter unit 220 is shown in FIG. 2 as being an in loop filter, in other configurations, the loop filter unit 220 may be implemented as a post loop filter. The filtered block 221 may also be referred to as filtered reconstructed block 221.

Embodiments of the video encoder 20 (respectively loop filter unit 220) may be configured to output loop filter parameters (such as sample adaptive offset information), e.g. directly or encoded via the entropy encoding unit 270, so that, e.g., a decoder 30 may receive and apply the same loop filter parameters or respective loop filters for decoding.

Decoded Picture Buffer

The decoded picture buffer (DPB) 230 may be a memory that stores reference pictures, or in general reference picture data, for encoding video data by video encoder 20. The DPB 230 may be formed by any of a variety of memory devices, such as dynamic random access memory (DRAM), including synchronous DRAM (SDRAM), magnetoresistive RAM (MRAM), resistive RAM (RRAM), or other types of memory devices. The decoded picture buffer (DPB) 230 may be configured to store one or more filtered blocks 221. The decoded picture buffer 230 may be further configured to store other previously filtered blocks, e.g. previously reconstructed and filtered blocks 221, of the same current picture or of different pictures, e.g. previously reconstructed pictures, and may provide complete previously reconstructed, i.e. decoded, pictures (and corresponding reference blocks and samples) and/or a partially reconstructed current picture (and corresponding reference blocks and samples), for example for inter prediction. The decoded picture buffer (DPB) 230 may be also configured to store one or more unfiltered reconstructed blocks 215, or in general unfiltered reconstructed samples, e.g. if the reconstructed block 215 is not filtered by loop filter unit 220, or any other further processed version of the reconstructed blocks or samples.

Mode Selection (Partitioning & Prediction)

The mode selection unit 260 comprises partitioning unit 262, inter-prediction unit 244 and intra-prediction unit 254, and is configured to receive or obtain original picture data, e.g. an original block 203 (current block 203 of the current picture 17), and reconstructed picture data, e.g. filtered and/or unfiltered reconstructed samples or blocks of the same (current) picture and/or from one or a plurality of previously decoded pictures, e.g. from decoded picture buffer 230 or other buffers (e.g. line buffer, not shown). The reconstructed picture data is used as reference picture data for prediction, e.g. inter-prediction or intra-prediction, to obtain a prediction block 265 or predictor 265.

Mode selection unit 260 may be configured to determine or select a partitioning for a current block prediction mode (including no partitioning) and a prediction mode (e.g. an intra or inter prediction mode) and generate a corresponding prediction block 265, which is used for the calculation of the residual block 205 and for the reconstruction of the reconstructed block 215.

Embodiments of the mode selection unit 260 may be configured to select the partitioning and the prediction mode (e.g. from those supported by or available for mode selection unit 260), which provide the best match or in other words the minimum residual (minimum residual means better compression for transmission or storage), or a minimum signaling overhead (minimum signaling overhead means better compression for transmission or storage), or which considers or balances both. The mode selection unit 260 may be configured to determine the partitioning and prediction mode based on rate distortion optimization (RDO), i.e. select the prediction mode which provides a minimum rate distortion. Terms like “best”, “minimum”, “optimum” etc. in this context do not necessarily refer to an overall “best”, “minimum”, “optimum”, etc. but may also refer to the fulfillment of a termination or selection criterion like a value exceeding or falling below a threshold or other constraints leading potentially to a “sub-optimum selection” but reducing complexity and processing time.

In other words, the partitioning unit 262 may be configured to partition the block 203 into smaller block partitions or sub-blocks (which form again blocks), e.g. iteratively using quad-tree-partitioning (QT), binary partitioning (BT) or triple-tree-partitioning (TT) or any combination thereof, and to perform, e.g., the prediction for each of the block partitions or sub-blocks, wherein the mode selection comprises the selection of the tree-structure of the partitioned block 203 and the prediction modes are applied to each of the block partitions or sub-blocks.

In the following the partitioning (e.g. by partitioning unit 260) and prediction processing (by inter-prediction unit 244 and intra-prediction unit 254) performed by an example video encoder 20 will be explained in more detail.

Partitioning

The partitioning unit 262 may partition (or split) a current block 203 into smaller partitions, e.g. smaller blocks of square or rectangular size. These smaller blocks (which may also be referred to as sub-blocks) may be further partitioned into even smaller partitions. This is also referred to tree-partitioning or hierarchical tree-partitioning, wherein a root block, e.g. at root tree-level 0 (hierarchy-level 0, depth 0), may be recursively partitioned, e.g. partitioned into two or more blocks of a next lower tree-level, e.g. nodes at tree-level 1 (hierarchy-level 1, depth 1), wherein these blocks may be again partitioned into two or more blocks of a next lower level, e.g. tree-level 2 (hierarchy-level 2, depth 2), etc. until the partitioning is terminated, e.g. because a termination criterion is fulfilled, e.g. a maximum tree depth or minimum block size is reached. Blocks which are not further partitioned are also referred to as leaf-blocks or leaf nodes of the tree. A tree using partitioning into two partitions is referred to as binary-tree (BT), a tree using partitioning into three partitions is referred to as ternary-tree (TT), and a tree using partitioning into four partitions is referred to as quad-tree (QT).

As mentioned before, the term “block” as used herein may be a portion, in particular a square or rectangular portion, of a picture. With reference, for example, to HEVC and VVC, the block may be or correspond to a coding tree unit (CTU), a coding unit (CU), prediction unit (PU), and transform unit (TU) and/or to the corresponding blocks, e.g. a coding tree block (CTB), a coding block (CB), a transform block (TB) or prediction block (PB).

For example, a coding tree unit (CTU) may be or comprise a CTB of luma samples, two corresponding CTBs of chroma samples of a picture that has three sample arrays, or a CTB of samples of a monochrome picture or a picture that is coded using three separate colour planes and syntax structures used to code the samples. Correspondingly, a coding tree block (CTB) may be an N×N block of samples for some value of N such that the division of a component into CTBs is a partitioning. A coding unit (CU) may be or comprise a coding block of luma samples, two corresponding coding blocks of chroma samples of a picture that has three sample arrays, or a coding block of samples of a monochrome picture or a picture that is coded using three separate colour planes and syntax structures used to code the samples. Correspondingly a coding block (CB) may be an M×N block of samples for some values of M and N such that the division of a CTB into coding blocks is a partitioning.

In embodiments, e.g., according to HEVC, a coding tree unit (CTU) may be split into CUs by using a quad-tree structure denoted as coding tree. The decision whether to code a picture area using inter-picture (temporal) or intra-picture (spatial) prediction is made at the CU level. Each CU can be further split into one, two or four PUs according to the PU splitting type. Inside one PU, the same prediction process is applied and the relevant information is transmitted to the decoder on a PU basis. After obtaining the residual block by applying the prediction process based on the PU splitting type, a CU can be partitioned into transform units (TUs) according to another quadtree structure similar to the coding tree for the CU.

In embodiments, e.g., according to the latest video coding standard currently in development, which is referred to as Versatile Video Coding (VVC), a combined Quad-tree and binary tree (QTBT) partitioning is for example used to partition a coding block. In the QTBT block structure, a CU can have either a square or rectangular shape. For example, a coding tree unit (CTU) is first partitioned by a quadtree structure. The quadtree leaf nodes are further partitioned by a binary tree or ternary (or triple) tree structure. The partitioning tree leaf nodes are called coding units (CUs), and that segmentation is used for prediction and transform processing without any further partitioning. This means that the CU, PU and TU have the same block size in the QTBT coding block structure. In parallel, multiple partition, for example, triple tree partition may be used together with the QTBT block structure.

In one example, the mode selection unit 260 of video encoder 20 may be configured to perform any combination of the partitioning techniques described herein.

As described above, the video encoder 20 is configured to determine or select the best or an optimum prediction mode from a set of (e.g. pre-determined) prediction modes. The set of prediction modes may comprise, e.g., intra-prediction modes and/or inter-prediction modes.

Intra-Prediction

The set of intra-prediction modes may comprise 35 different intra-prediction modes, e.g. non-directional modes like DC (or mean) mode and planar mode, or directional modes, e.g. as defined in HEVC, or may comprise 67 different intra-prediction modes, e.g. non-directional modes like DC (or mean) mode and planar mode, or directional modes, e.g. as defined for VVC.

The intra-prediction unit 254 is configured to use reconstructed samples of neighboring blocks of the same current picture to generate an intra-prediction block 265 according to an intra-prediction mode of the set of intra-prediction modes.

The intra prediction unit 254 (or in general the mode selection unit 260) is further configured to output intra-prediction parameters (or in general information indicative of the selected intra prediction mode for the block) to the entropy encoding unit 270 in form of syntax elements 266 for inclusion into the encoded picture data 21, so that, e.g., the video decoder 30 may receive and use the prediction parameters for decoding.

Inter-Prediction

The set of (or possible) inter-prediction modes depends on the available reference pictures (i.e. previous at least partially decoded pictures, e.g. stored in DBP 230) and other inter-prediction parameters, e.g. whether the whole reference picture or only a part, e.g. a search window area around the area of the current block, of the reference picture is used for searching for a best matching reference block, and/or e.g. whether pixel interpolation is applied, e.g. half/semi-pel and/or quarter-pel interpolation, or not.

Additional to the above prediction modes, skip mode and/or direct mode may be applied.

The inter prediction unit 244 may include a motion estimation (ME) unit and a motion compensation (MC) unit (both not shown in FIG. 2). The motion estimation unit may be configured to receive or obtain the picture block 203 (current picture block 203 of the current picture 17) and a decoded picture 231, or at least one or a plurality of previously reconstructed blocks, e.g. reconstructed blocks of one or a plurality of other/different previously decoded pictures 231, for motion estimation. E.g. a video sequence may comprise the current picture and the previously decoded pictures 231, or in other words, the current picture and the previously decoded pictures 231 may be part of or form a sequence of pictures forming a video sequence.

The encoder 20 may, e.g., be configured to select a reference block from a plurality of reference blocks of the same or different pictures of the plurality of other pictures and provide a reference picture (or reference picture index) and/or an offset (spatial offset) between the position (x, y coordinates) of the reference block and the position of the current block as inter prediction parameters to the motion estimation unit. This offset is also called motion vector (MV).

The motion compensation unit is configured to obtain, e.g. receive, an inter prediction parameter and to perform inter prediction based on or using the inter prediction parameter to obtain an inter prediction block 265. Motion compensation, performed by the motion compensation unit, may involve fetching or generating the prediction block based on the motion/block vector determined by motion estimation, possibly performing interpolations to sub-pixel precision. Interpolation filtering may generate additional pixel samples from known pixel samples, thus potentially increasing the number of candidate prediction blocks that may be used to code a picture block. Upon receiving the motion vector for the PU of the current picture block, the motion compensation unit may locate the prediction block to which the motion vector points in one of the reference picture lists.

The motion compensation unit may also generate syntax elements associated with the blocks and video slices for use by video decoder 30 in decoding the picture blocks of the video slice. In addition or as an alternative to slices and respective syntax elements, tile groups and/or tiles and respective syntax elements may be generated or used.

Entropy Coding

The entropy encoding unit 270 is configured to apply, for example, an entropy encoding algorithm or scheme (e.g. a variable length coding (VLC) scheme, an context adaptive VLC scheme (CAVLC), an arithmetic coding scheme, a binarization, a context adaptive binary arithmetic coding (CABAC), syntax-based context-adaptive binary arithmetic coding (SBAC), probability interval partitioning entropy (PIPE) coding or another entropy encoding methodology or technique) or bypass (no compression) on the quantized coefficients 209, inter prediction parameters, intra prediction parameters, loop filter parameters and/or other syntax elements to obtain encoded picture data 21 which can be output via the output 272, e.g. in the form of an encoded bitstream 21, so that, e.g., the video decoder 30 may receive and use the parameters for decoding. The encoded bitstream 21 may be transmitted to video decoder 30, or stored in a memory for later transmission or retrieval by video decoder 30.

Other structural variations of the video encoder 20 can be used to encode the video stream. For example, a non-transform based encoder 20 can quantize the residual signal directly without the transform processing unit 206 for certain blocks or frames. In another implementation, an encoder 20 can have the quantization unit 208 and the inverse quantization unit 210 combined into a single unit.

Decoder and Decoding Method

FIG. 3 shows an example of a video decoder 30 that is configured to implement the techniques of this present application. The video decoder 30 is configured to receive encoded picture data 21 (e.g. encoded bitstream 21), e.g. encoded by encoder 20, to obtain a decoded picture 331. The encoded picture data or bitstream comprises information for decoding the encoded picture data, e.g. data that represents picture blocks of an encoded video slice (and/or tile groups or tiles) and associated syntax elements.

In the example of FIG. 3, the decoder 30 comprises an entropy decoding unit 304, an inverse quantization unit 310, an inverse transform processing unit 312, a reconstruction unit 314 (e.g. a summer 314), a loop filter 320, a decoded picture buffer (DBP) 330, a mode application unit 360, an inter prediction unit 344 and an intra prediction unit 354. Inter prediction unit 344 may be or include a motion compensation unit. Video decoder 30 may, in some examples, perform a decoding pass generally reciprocal to the encoding pass described with respect to video encoder 100 from FIG. 2.

As explained with regard to the encoder 20, the inverse quantization unit 210, the inverse transform processing unit 212, the reconstruction unit 214 the loop filter 220, the decoded picture buffer (DPB) 230, the inter prediction unit 344 and the intra prediction unit 354 are also referred to as forming the “built-in decoder” of video encoder 20. Accordingly, the inverse quantization unit 310 may be identical in function to the inverse quantization unit 110, the inverse transform processing unit 312 may be identical in function to the inverse transform processing unit 212, the reconstruction unit 314 may be identical in function to reconstruction unit 214, the loop filter 320 may be identical in function to the loop filter 220, and the decoded picture buffer 330 may be identical in function to the decoded picture buffer 230. Therefore, the explanations provided for the respective units and functions of the video 20 encoder apply correspondingly to the respective units and functions of the video decoder 30.

Entropy Decoding

The entropy decoding unit 304 is configured to parse the bitstream 21 (or in general encoded picture data 21) and perform, for example, entropy decoding to the encoded picture data 21 to obtain, e.g., quantized coefficients 309 and/or decoded coding parameters (not shown in FIG. 3), e.g. any or all of inter prediction parameters (e.g. reference picture index and motion vector), intra prediction parameter (e.g. intra prediction mode or index), transform parameters, quantization parameters, loop filter parameters, and/or other syntax elements. Entropy decoding unit 304 maybe configured to apply the decoding algorithms or schemes corresponding to the encoding schemes as described with regard to the entropy encoding unit 270 of the encoder 20. Entropy decoding unit 304 may be further configured to provide inter prediction parameters, intra prediction parameter and/or other syntax elements to the mode application unit 360 and other parameters to other units of the decoder 30. Video decoder 30 may receive the syntax elements at the video slice level and/or the video block level. In addition or as an alternative to slices and respective syntax elements, tile groups and/or tiles and respective syntax elements may be received and/or used.

Inverse Quantization

The inverse quantization unit 310 may be configured to receive quantization parameters (QP) (or in general information related to the inverse quantization) and quantized coefficients from the encoded picture data 21 (e.g. by parsing and/or decoding, e.g. by entropy decoding unit 304) and to apply based on the quantization parameters an inverse quantization on the decoded quantized coefficients 309 to obtain dequantized coefficients 311, which may also be referred to as transform coefficients 311. The inverse quantization process may include use of a quantization parameter determined by video encoder 20 for each video block in the video slice (or tile or tile group) to determine a degree of quantization and, likewise, a degree of inverse quantization that should be applied.

Inverse Transform

Inverse transform processing unit 312 may be configured to receive dequantized coefficients 311, also referred to as transform coefficients 311, and to apply a transform to the dequantized coefficients 311 in order to obtain reconstructed residual blocks 213 in the sample domain. The reconstructed residual blocks 213 may also be referred to as transform blocks 313. The transform may be an inverse transform, e.g., an inverse DCT, an inverse DST, an inverse integer transform, or a conceptually similar inverse transform process. The inverse transform processing unit 312 may be further configured to receive transform parameters or corresponding information from the encoded picture data 21 (e.g. by parsing and/or decoding, e.g. by entropy decoding unit 304) to determine the transform to be applied to the dequantized coefficients 311.

Reconstruction

The reconstruction unit 314 (e.g. adder or summer 314) may be configured to add the reconstructed residual block 313, to the prediction block 365 to obtain a reconstructed block 315 in the sample domain, e.g. by adding the sample values of the reconstructed residual block 313 and the sample values of the prediction block 365.

Filtering

The loop filter unit 320 (either in the coding loop or after the coding loop) is configured to filter the reconstructed block 315 to obtain a filtered block 321, e.g. to smooth pixel transitions, or otherwise improve the video quality. The loop filter unit 320 may comprise one or more loop filters such as a de-blocking filter, a sample-adaptive offset (SAO) filter or one or more other filters, e.g. a bilateral filter, an adaptive loop filter (ALF), a sharpening, a smoothing filters or a collaborative filters, or any combination thereof. Although the loop filter unit 320 is shown in FIG. 3 as being an in loop filter, in other configurations, the loop filter unit 320 may be implemented as a post loop filter.

Decoded Picture Buffer

The decoded video blocks 321 of a picture are then stored in decoded picture buffer 330, which stores the decoded pictures 331 as reference pictures for subsequent motion compensation for other pictures and/or for output respectively display.

The decoder 30 is configured to output the decoded picture 311, e.g. via output 312, for presentation or viewing to a user.

Prediction

The inter prediction unit 344 may be identical to the inter prediction unit 244 (in particular to the motion compensation unit) and the intra prediction unit 354 may be identical to the inter prediction unit 254 in function, and performs split or partitioning decisions and prediction based on the partitioning and/or prediction parameters or respective information received from the encoded picture data 21 (e.g. by parsing and/or decoding, e.g. by entropy decoding unit 304). Mode application unit 360 may be configured to perform the prediction (intra or inter prediction) per block based on reconstructed pictures, blocks or respective samples (filtered or unfiltered) to obtain the prediction block 365.

When the video slice is coded as an intra coded (I) slice, intra prediction unit 354 of mode application unit 360 is configured to generate prediction block 365 for a picture block of the current video slice based on a signaled intra prediction mode and data from previously decoded blocks of the current picture. When the video picture is coded as an inter coded (i.e., B, or P) slice, inter prediction unit 344 (e.g. motion compensation unit) of mode application unit 360 is configured to produce prediction blocks 365 for a video block of the current video slice based on the motion vectors and other syntax elements received from entropy decoding unit 304. For inter prediction, the prediction blocks may be produced from one of the reference pictures within one of the reference picture lists. Video decoder 30 may construct the reference frame lists, List 0 and List 1, using default construction techniques based on reference pictures stored in DPB 330. The same or similar may be applied for or by embodiments using tile groups (e.g. video tile groups) and/or tiles (e.g. video tiles) in addition or alternatively to slices (e.g. video slices), e.g. a video may be coded using I, P or B tile groups and/or tiles.

Mode application unit 360 is configured to determine the prediction information for a video block of the current video slice by parsing the motion vectors or related information and other syntax elements, and uses the prediction information to produce the prediction blocks for the current video block being decoded. For example, the mode application unit 360 uses some of the received syntax elements to determine a prediction mode (e.g., intra or inter prediction) used to code the video blocks of the video slice, an inter prediction slice type (e.g., B slice, P slice, or GPB slice), construction information for one or more of the reference picture lists for the slice, motion vectors for each inter encoded video block of the slice, inter prediction status for each inter coded video block of the slice, and other information to decode the video blocks in the current video slice. The same or similar may be applied for or by embodiments using tile groups (e.g. video tile groups) and/or tiles (e.g. video tiles) in addition or alternatively to slices (e.g. video slices), e.g. a video may be coded using I, P or B tile groups and/or tiles.

Embodiments of the video decoder 30 as shown in FIG. 3 may be configured to partition and/or decode the picture by using slices (also referred to as video slices), wherein a picture may be partitioned into or decoded using one or more slices (typically non-overlapping), and each slice may comprise one or more blocks (e.g. CTUs).

Embodiments of the video decoder 30 as shown in FIG. 3 may be configured to partition and/or decode the picture by using tile groups (also referred to as video tile groups) and/or tiles (also referred to as video tiles), wherein a picture may be partitioned into or decoded using one or more tile groups (typically non-overlapping), and each tile group may comprise, e.g. one or more blocks (e.g. CTUs) or one or more tiles, wherein each tile, e.g. may be of rectangular shape and may comprise one or more blocks (e.g. CTUs), e.g. complete or fractional blocks.

Other variations of the video decoder 30 can be used to decode the encoded picture data 21. For example, the decoder 30 can produce the output video stream without the loop filtering unit 320. For example, a non-transform based decoder 30 can inverse-quantize the residual signal directly without the inverse-transform processing unit 312 for certain blocks or frames. In another implementation, the video decoder 30 can have the inverse-quantization unit 310 and the inverse-transform processing unit 312 combined into a single unit.

It should be understood that, in the encoder 20 and the decoder 30, a processing result of a current step may be further processed and then output to the next step. For example, after interpolation filtering, motion vector derivation or loop filtering, a further operation, such as Clip or shift, may be performed on the processing result of the interpolation filtering, motion vector derivation or loop filtering.

It should be noted that further operations may be applied to the derived motion vectors of current block (including but not limit to control point motion vectors of affine mode, sub-block motion vectors in affine, planar, ATMVP modes, temporal motion vectors, and so on). For example, the value of motion vector is constrained to a predefined range according to its representing bit. If the representing bit of motion vector is bitDepth, then the range is −2{circumflex over ( )}(bitDepth−1)˜2{circumflex over ( )}(bitDepth−1)−1, where “{circumflex over ( )}” means exponentiation. For example, if bitDepth is set equal to 16, the range is −32768˜32767; if bitDepth is set equal to 18, the range is −131072˜131071. For example, the value of the derived motion vector (e.g. the MVs of four 4×4 sub-blocks within one 8×8 block) is constrained such that the max difference between integer parts of the four 4×4 sub-block MVs is no more than N pixels, such as no more than 1 pixel. Here provides two methods for constraining the motion vector according to the bitDepth.

Method 1: remove the overflow MSB (most significant bit) by flowing operations

ux=(mvx+2^(bitDepth))%2^(bitDepth)  (1)

mvx=(ux>=2^(bitDepth-1))?(ux−2^(bitDepth)):ux  (2)

uy=(mvy+2^(bitDepth))%2^(bitDepth)  (3)

mvy=(uy>=2^(bitDepth-1))?(uy−2^(bitDepth)):uy  (4)

where mvx is a horizontal component of a motion vector of an image block or a sub-block, mvy is a vertical component of a motion vector of an image block or a sub-block, and ux and uy indicates an intermediate value.

For example, if the value of mvx is −32769, after applying formula (1) and (2), the resulting value is 32767. In computer system, decimal numbers are stored as two's complement. The two's complement of −32769 is 1,0111,1111,1111,1111 (17 bits), then the MSB is discarded, so the resulting two's complement is 0111,1111,1111,1111 (decimal number is 32767), which is same as the output by applying formula (1) and (2).

ux=(mvpx+mvdx+2^(bitDepth))%2^(bitDepth)  (5)

mvx=(ux>=2^(bitDepth-1))?(ux−2^(bitDepth)):ux  (6)

uy=(mvpy+mvdy+2^(bitDepth))%2^(bitDepth)  (7)

mvy=(uy>=2^(bitDepth-1))?(uy−2^(bitDepth)):uy  (8)

The operations may be applied during the sum of mvp and mvd, as shown in formula (5) to (8).

Method 2: remove the overflow MSB by clipping the value

vx=Clip3(−2^(bitDepth-1),2^(bitDepth-1)−1,vx)

vy=Clip3(−2^(bitDepth-1),2^(bitDepth-1)−1,vy)

where vx is a horizontal component of a motion vector of an image block or a sub-block, vy is a vertical component of a motion vector of an image block or a sub-block; x, y and z respectively correspond to three input value of the MV clipping process, and the definition of function Clip3 is as follow:

${{Clip}\; 3\left( {x,y,z} \right)} = \left\{ \begin{matrix} {x;} & {z < x} \\ {y;} & {z > y} \\ {z;} & {otherwise} \end{matrix} \right.$

FIG. 4 is a schematic diagram of a video coding device 400 according to an embodiment of the disclosure. The video coding device 400 is suitable for implementing the disclosed embodiments as described herein. In an embodiment, the video coding device 400 may be a decoder such as video decoder 30 of FIG. 1A or an encoder such as video encoder 20 of FIG. 1A.

The video coding device 400 comprises ingress ports 410 (or input ports 410) and receiver units (Rx) 420 for receiving data; a processor, logic unit, or central processing unit (CPU) 430 to process the data; transmitter units (Tx) 440 and egress ports 450 (or output ports 450) for transmitting the data; and a memory 460 for storing the data. The video coding device 400 may also comprise optical-to-electrical (OE) components and electrical-to-optical (EO) components coupled to the ingress ports 410, the receiver units 420, the transmitter units 440, and the egress ports 450 for egress or ingress of optical or electrical signals.

The processor 430 is implemented by hardware and software. The processor 430 may be implemented as one or more CPU chips, cores (e.g., as a multi-core processor), FPGAs, ASICs, and DSPs. The processor 430 is in communication with the ingress ports 410, receiver units 420, transmitter units 440, egress ports 450, and memory 460. The processor 430 comprises a coding module 470. The coding module 470 implements the disclosed embodiments described above. For instance, the coding module 470 implements, processes, prepares, or provides the various coding operations. The inclusion of the coding module 470 therefore provides a substantial improvement to the functionality of the video coding device 400 and effects a transformation of the video coding device 400 to a different state. Alternatively, the coding module 470 is implemented as instructions stored in the memory 460 and executed by the processor 430.

The memory 460 may comprise one or more disks, tape drives, and solid-state drives and may be used as an over-flow data storage device, to store programs when such programs are selected for execution, and to store instructions and data that are read during program execution. The memory 460 may be, for example, volatile and/or non-volatile and may be a read-only memory (ROM), random access memory (RAM), ternary content-addressable memory (TCAM), and/or static random-access memory (SRAM).

FIG. 5 is a simplified block diagram of an apparatus 500 that may be used as either or both of the source device 12 and the destination device 14 from FIG. 1 according to an exemplary embodiment.

A processor 502 in the apparatus 500 can be a central processing unit. Alternatively, the processor 502 can be any other type of device, or multiple devices, capable of manipulating or processing information now-existing or hereafter developed. Although the disclosed implementations can be practiced with a single processor as shown, e.g., the processor 502, advantages in speed and efficiency can be achieved using more than one processor.

A memory 504 in the apparatus 500 can be a read only memory (ROM) device or a random access memory (RAM) device in an implementation. Any other suitable type of storage device can be used as the memory 504. The memory 504 can include code and data 506 that is accessed by the processor 502 using a bus 512. The memory 504 can further include an operating system 508 and application programs 510, the application programs 510 including at least one program that permits the processor 502 to perform the methods described here. For example, the application programs 510 can include applications 1 through N, which further include a video coding application that performs the methods described here.

The apparatus 500 can also include one or more output devices, such as a display 518. The display 518 may be, in one example, a touch sensitive display that combines a display with a touch sensitive element that is operable to sense touch inputs. The display 518 can be coupled to the processor 502 via the bus 512.

Although depicted here as a single bus, the bus 512 of the apparatus 500 can be composed of multiple buses. Further, the secondary storage 514 can be directly coupled to the other components of the apparatus 500 or can be accessed via a network and can comprise a single integrated unit such as a memory card or multiple units such as multiple memory cards. The apparatus 500 can thus be implemented in a wide variety of configurations.

Parameter Sets

Parameter sets in state of the art codecs are fundamentally similar and share the same basic design goals—namely bit rate efficiency, error resiliency, and providing systems layer interfaces. There is a hierarchy of parameter sets in HEVC (H.265), including the Video Parameter Set (VPS), Sequence Parameter Set (SPS) and Picture Parameter Set (PPS) which are similar to their counterparts in AVC and VVC. Each slice references a single active PPS, SPS and VPS to access information used for decoding the slice. The PPS contains information which applies to all slices in a picture, and hence all slices in a picture must refer to the same PPS. The slices in different pictures are also allowed to refer to the same PPS. Similarly, the SPS contains information which applies to all pictures in the same coded video sequence.

While the PPS may differ for separate pictures, it is common for many or all pictures in a coded video sequence to refer to the same PPS. Reusing parameter sets is bit rate efficient because it avoids the necessity to send shared information multiple times. It is also loss robust because it allows parameter set content to be carried by some more reliable external communication link or to be repeated frequently within the bitstream to ensure that it will not get lost.

In HEVC, to identify for a given slice the active parameter set at each level of the parameter set type hierarchy, each slice header contains a PPS identifier which references a particular PPS. Within the PPS is an identifier that references a particular SPS. In turn, within the SPS is an identifier that references a particular VPS.

A parameter set is activated when the current coded slice to be decoded references that parameter set. All active parameter sets must be available to the decoder when they are first referenced. Parameter sets may be sent in-band or out-of-band, and may be sent repeatedly.

Parameter sets may be received in any order.

These parameter set features provide improved error resiliency, by overcoming some network loss of parameter sets. Additionally, the use of parameter sets allows an individual slice to be decoded even if another slice in the same picture suffered network loss, compared to if a picture header containing the same information was present in a subset of the slices of a picture.

The Picture Parameter Set (PPS)

The PPS contains parameters that may change for different pictures within the same coded video sequence. However, multiple pictures may refer to the same PPS, even those with different slice coding types (I, P, and B). Including these parameters within picture parameter sets rather than within the slice header can improve bit rate efficiency and provide error resiliency when the PPS is transmitted more reliably.

The PPS contains a PPS identifier, as well as an index to a reference SPS. The remaining parameters describe coding tools used in the slices which refer to the PPS. Coding tools can be enabled or disabled, including tiles, weighted prediction, sign data hiding, temporal motion vector prediction etc. Coding tool parameters signaled in the PPS include the number of reference indices, initial quantization parameter (QP), and chroma QP offsets. Coding tool parameters may also be signaled in a PPS, e.g. deblocking filter controls, tile configurations, and scaling list data. An example PPS is depicted in FIGS. 6 and 7, according to the document Versatile Video Coding (Draft 6) of Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 (available under http://phenix.it-sudparis.eu/jvet/, document no: Document: JVET-02001-vE).

In FIG. 7 a section of the PPS is depicted. In this figure the syntax element constant_slice_header_params_enabled_flag (constant_slice_header_params_enabled_flag) indicates whether there are contant parameters in PPS. When the value of constant_slice_header_params_enabled_flag is equal to 1, additional syntax elements such as pps_temporal_mvp_enabled_idc (730) is included in the PPS. The pps_temporal_mvp_enabled_idc is a syntax element that might be present in a PPS and controls the application of temporal motion vector prediction and indicates the following:

If the value of the syntax element is 1, then temporal MV prediction is disabled in slices that refer to the said PPS.

If the value of the syntax element is 2, then temporal MV prediction is enabled in slices that refer to the said PPS.

If the value of the syntax element is 0, then a second syntax element is included in the slice header to control the application of temporal MV prediction of the slice. According to the prior art (JVET-02001-vE), pps_temporal_mvp_enabled_idc equal to 0 specifies that the syntax element slice_temporal_mvp_enabled_flag is present in the slice header of slices with slice_type not equal to I of slices referring to the PPS. pps_temporal_mvp_enabled_idc equal to 1 or 2 specifies that slice_temporal_mvp_enabled_flag is not present in slice header of slices referring to the PPS. pps_temporal_mvp_enabled_idc equal to 3 is reserved for future use by ITU-T|ISO/IEC.

In FIG. 7, another example is depicted which is dep_quant_enabled_flag (720). pps_dep_quant_enabled_idc equal to 0 specifies that the syntax element dep_quant_enabled_flag is present in slice header of slices referring to the PPS. pps_dep_quant_enabled_idc equal to 1 or 2 specifies that the syntax element dep_quant_enabled_flag is not present in slice header of slices referring to the PPS. pps_dep_quant_enabled_idc equal to 3 is reserved for future use by ITU-T|ISO/IEC. When the dep_quant_enabled_flag controls the application of dependent quantization of the slice, a value of zero corresponds to disabling dependent quantization and a value of 1 corresponds to enabling of dependent quantization. When pps_dep_quant_enabled_idc is not equal to zero, dep_quant_enabled_flag is not included in the slice header, instead its value is inferred to be equal to pps_dep_quant_enabled_idc−1.

The syntax elements that are included in the PPS when constant_slice_header_params_enabled_flag is true is depicted in FIG. 7. The syntax elements specify default that are included in the PPS when constant_slice_header_params_enabled_flag is true have the following common property:

Each syntax element in the PPS has a corresponding syntax element in slice header. Example, pps_dep_quant_enabled_idc is the syntax element in PPS, whereas dep_quant_enabled_flag is the corresponding syntax element in the slice header.

If the syntax element in the PPS has a value of zero, then the slice header counterpart is present (is included in) the slice header. Otherwise slice header syntax element is absent in the slice header.

If the syntax element in the PPS has a value different from zero, then the value of the corresponding slice header syntax element is inferred according to the value of the syntax element in the PPS. For example, if value of pps_dep_quant_enabled_idc is equal to 1, the value of dep_quant_enabled_idc is inferred to be pps_dep_quant_enabled_idc−1=0.

In VVC and HEVC, the partitions of a same video picture (slices, tiles, sub-pictures, bricks etc.) must refer to the same picture parameter set. It is the requirement of the coding standard, since a PPS might include parameters that apply to the entirety of a picture. For example, the syntax elements that are include in the bracket (610) describe how a picture is partitioned into multiple tile partitions as follows:

-   -   tile_cols_width_minus1 specifies the width of each tile in unit         of CTBs when a picture is evenly divided into tiles     -   tile_rows_height_minus1 specifies the height of each tile in         unit of CTBs when a picture is evenly divided into tiles.     -   num_tile_columns_minus1 specifies the number of tile columns in         a picture     -   num_tile_rows_minus1 specifies the number of tile rows in a         picture

A picture that refers to a PPS is divided into multiple tile partitions that are specified according to the syntax elements above. If two slices of a same picture refer to 2 different PPS, it might cause a conflicting situation since each PPS might indicate different types of tile partitioning of the picture. Therefore, it is prohibited for 2 slices (or in general 2 partitions of a picture) to refer to 2 different PPSes.

In VVC various picture partitioning mechanism are defined, they are called slices, tiles, bricks and sub-pictures. In the present application a picture partition is a general term to refer to any of the slice, tiles, bricks, or sub-pictures. A picture partition usually refers to a part of the frame that is coded independently of the other parts in the same picture.

Adaptation Parameter Set

In state of the art video codecs the bitstream consists of a sequence of data units called network abstraction layer (NAL) units. Some NAL units contain parameter sets that carry high-level information regarding the entire coded video sequence or a subset of the pictures within it. Other NAL units carry coded samples in the form of slices that belong to one of the various picture types. Adaptation parameter set (APS) is a parameter set that is used to encapsulate the ALF filter control data (e.g. filter coefficients).

FIG. 8 exemplifies an adaptation parameter set according to document Versatile Video Coding (Draft 6) of Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 (available under http://phenix.it-sudparis.eu/jvet/, document no: Document: JVET-02001-vE).

The Slice Header

The slice segment header contains an index to a reference PPS. The slice segment header contains data identifying the starting address of the slice. Some parameters are included only in the first slice segment of a slice, including the slice type (I, P, or B), picture output flag, etc. The presence of some coding tool parameters are present in the slice header if the tools were enabled in the SPS or PPS, including enabling SAO separately for luma and chroma, enabling deblocking filter operation across slices, and an initial slice quantization parameter (QP) value. Deblocking filter parameters may either be present in the slice segment header or the PPS.

Coded Slice

Each coded slice typically consists of a slice header followed by slice data. The slice header carries control information for the slice, and the slice data carries the coded samples. FIGS. 9 and 11 exemplify a slice header according to document JVET-02001-vE. Furthermore, the FIG. 10a exemplifies the coding tree unit syntax structure which is part of the slice data.

Each slice is independent of other slices in the sense that the information carried in the slice is coded without any dependency on data from other slices within the same picture.

Picture Header

Picture header (PH) is a syntax structure containing syntax elements that apply to all slices of a coded picture. The following table exemplifies a picture header according to document JVET-P1006 (http://phenix.it-sudparis.eu/jvet/doc end user/documents/16_Geneva/wg11/JVET-P1006-v2.zip). For example, pic_temporal_mvp_enabled_flag specifies whether temporal motion vector predictors can be used for inter prediction for all slices associated with the picture header. If pic_temporal_mvp_enabled_flag is equal to 0, the syntax elements of the slices associated with the picture header shall be constrained such that no temporal motion vector predictor is used in decoding of the slices. Otherwise (pic_temporal_mvp_enabled_flag is equal to 1), temporal motion vector predictors may be used in decoding of the slices associated with the picture header.

The following table is an example of the picture header syntax:

Descriptor  picture _header_rbsp( ) {   non_reference_picture_flag u(1)   gdr_pic_flag u(1)   no_output_of_prior_pics_flag u(1)   if( gdr_pic_flag )    recovery_poc_cnt ue(v)   ph_pic_parameter_set_id ue(v)   if( sps_subpic_id_present_flag && !sps_subpic_id_signalling_flag ) {   ph_subpic_id_signalling_present_flag u(1)   if( ph_subpics_id_signalling_present_flag ) {    ph_subpic_id_len_minus1 ue(v)    for( i = 0; i < NumSubPics; i++ )     ph_subpic_id[ i ] u(v)   }  }  if( !sps_loop_filter_across_virtual_boundaries_disabled_present_flag ) {    ph_loop_filter_across_virtual_boundaries_disabled_present_flag u(1)    if( ph_loop_filter_across_virtual_boundaries_disabled_present_flag ) {    ph_num_ver_virtual_boundaries u(2)    for( i = 0; i < ph_num_ver_virtual_boundaries; i++ )     ph_virtual_boundaries_pos_x[ i ] u(13)    ph_num_hor_virtual_boundaries u(2)    for( i = 0; i < ph_num_hor_virtual_boundaries; i++ )     ph_virtual_boundaries_pos_y[ i ] u(13)   }  }   if( separate_colour_plane flag = = 1 )    colour_plane_id u(2)   if( output_flag_present_flag )    pic_output_flag u(1)   pic_rpl_present_flag u(1)   if( pic_rpl_present_flag ) {    for( i = 0; i < 2; i++ ) {    if( num_ref_pic_lists_in_sps[ i ] > 0 && !pps_ref_pic_list_sps_idc[ i ] &&      ( i = = 0 | | ( i = = 1 && rpl1_idx_present_flag ) ) )     pic_rpl_sps_flag[ i ] u(1)    if( pic_rpl_sps_flag[ i ] ) {     if( num_ref_pic_lists_in_sps[ i ] > 1 &&      ( i = = 0 | | ( i = = 1 && rpl1_idx_present_flag ) ) )      pic_rpl_idx[ i ] u(v)     } else     ref_pic_list_struct( i, num_ref_pic_lists_in_sps[ i ] )    for( j = 0; j < NumLtrpEntries[ i ][ RplsIdx[ i ] ]; j++ ) {      if( ltrp_in_slice_header_flag[ i ][ RplsIdx[ i ] ] )      pic_poc_lsb_lt[ i ][ j ] u(v)     pic_delta_poc_msb_present_flag[ i ][ j ] u(1)     if( pic_delta_poc_msb_present_flag[ i ][ j ] )      pic_delta_poc_msb_cycle_lt[ i ][ j ] ue(v)     }    }   }   if( partition_constraints_override_enabled_flag ) {    partition_constraints_override_flag ue(v)    if( partition_constraints_override_flag ) {     pic_log2_diff_min_qt_min_cb_intra_slice_luma ue(v)     pic_log2_diff_min_qt_min_cb_inter_slice ue(v)     pic_max_mtt_hierarchy_depth_inter_slice ue(v)     pic_max_mtt_hierarchy_depth_intra_slice_luma ue(v)     if( pic_max_mtt_hierarchy_depth_intra_slice_luma != 0 ) {      pic_log2_diff_max_bt_min_qt_intra_slice_luma ue(v)      pic_log2_diff_max_tt_min_qt_intra_slice_luma ue(v)     }     if( pic_max_mtt_hierarchy_depth_inter_slice != 0 ) {      pic_log2_diff_max_bt_min_qt_inter_slice ue(v)      pic_log2_diff_max_tt_min_qt_inter_slice ue(v)     }     if( qtbtt_dual_tree_intra_flag ) {      pic_log2_diff_min_qt_min_cb_intra_slice_chroma ue(v)      pic_max_mtt_hierarchy_depth_intra_slice_chroma ue(v)      if( pic_max_mtt_hierarchy_depth_intra_slice_chroma != 0 ) {       pic_log2_diff_max_bt_min_qt_intra_slice_chroma ue(v)       pic_log2_diff_max_tt_min_qt_intra_slice_chroma ue(v)      }     }    }   }   if( cu_qp_delta_enabled_flag ) {    pic_cu_qp_delta_subdiv_intra_slice ue(v)    pic_cu_qp_delta_subdiv_inter_slice ue(v)   }   if( cu_chroma_qp_offset_enabled_flag ) {    pic_cu_chroma_qp_offset_subdiv_intra_slice ue(v)    pic_cu_chroma_qp_offset_subdiv_inter_slice ue(v)   }   if( sps_temporal_mvp_enabled_flag && !pps_temporal_mvp_enabled_idc )    pic_temporal_mvp_enabled_flag u(1)   if(!pps_mvd_l1_zero_idc )    mvd_l1_zero_flag u(1)   if( !pps_six_minus_max_num_merge_cand_plus1 )    pic_six_minus_max_num_merge_cand ue(v)   if( sps_affine_enabled_flag &&    !pps_five_minus_max_num_subblock_merge_cand_plus1 )    pic_five_minus_max_num_subblock_merge_cand ue(v)   if( sps_fpel_mmvd_enabled_flag )    pic_fpel_mmvd_enabled_flag u(1)   if( sps_bdof_dmvr_slice_present_flag )    pic_disable_bdof_dmvr_flag u(1)   if( sps_triangle_enabled_flag && MaxNumMergeCand >= 2 &&  !pps_max_num_merge_cand_minus_max_num_triangle_cand_minus1 )    pic_max_num_merge_cand_minus_max_num_triangle_cand ue(v)   if ( sps_ibc_enabled_flag )    pic_six_minus_max_num_ibc_merge_cand ue(v)   if( sps_joint_cbcr_enabled_flag )    pic_joint_cbcr_sign_flag u(1)   if( sps_sao_enabled_flag ) {    pic_sao_enabled_present_flag u(1)    if( pic_sao_enabled_present_flag ) {     pic_sao_luma_enabled_flag u(1)     if(ChromaArrayType != 0 )      pic_sao_chroma_enabled_flag u(1)    }   }   if( sps_alf_enabled_flag ) {    pic_alf_enabled_present_flag u(1)    if( pic_alf_enabled_present_flag ) {     pic_alf_enabled_flag u(1)     if( pic_alf_enabled_flag ) {      pic_num_alf_aps_ids_luma u(3)      for( i = 0; i < pic_num_alf_aps_ids_luma; i++ )       pic_alf_aps_id_luma[ i ] u(3)      if( ChromaArrayType != 0 )       pic_alf_chroma_idc u(2)      if( pic_alf_chroma_idc )       pic_alf_aps_id_chroma u(3)     }    }   }   if ( !pps_dep_quant_enabled_flag )    pic_dep_quant_enabled_flag u(1)   if( !pic_dep_quant_enabled_flag )    sign_data_hiding_enabled_flag u(1)   if( deblocking_filter_override_enabled_flag ) {    pic_deblocking_filter_override_present_flag u(1)    if( pic_deblocking_filter_override_present_flag ) {     pic_deblocking_filter_override_flag u(1)     if( pic_deblocking_filter_override_flag ) {      pic_deblocking_filter_disabled_flag u(1)      if( !pic_deblocking_filter_disabled_flag ) {       pic_beta_offset_div2 se(v)       pic_tc_offset_div2 se(v)      }     }    }   }   if( sps_lmcs_enabled_flag ) {    pic_lmcs_enabled_flag u(1)    if( pic_lmcs_enabled_flag ) {     pic_lmcs_aps_id u(2)     if( ChromaArrayType != 0 )      pic_chroma_residual_scale_flag u(1)    }   }   if( sps_scaling_list_enabled_flag ) {    pic_scaling_list_present_flag u(1)    if( pic_scaling_list_present_flag )     pic_scaling_list_aps_id u(3)   }   if( picture_header_extension_present_flag ) {    ph_extension_length ue(v)    for( i = 0; i < ph_extension_length; i++)     ph_extension_data_byte[ i ] u(8)   }   r bsp_trailing_bits( )  }

The picture header is designed for all picture types, i.e. I picture, P picture, and B picture. An I picture contains only intra-predicted block, while a P or B picture contain inter-predicted block. The difference between P and B pictures is that a B picture can contain an inter-predicted block with bi-directional prediction while in P pictures only uni-directional inter prediction is allowed. Note in P or B pictures, there might also intra-predicted blocks.

In the picture header, there are quite a few syntax elements that are applicable for inter prediction only, namely, only for P and B picture. These elements are not necessary for I pictures.

Embodiments of this specification propose to introduce a flag indicating whether a current picture is an I picture or not. When the current picture is I picture, all syntax elements designed for inter prediction is not signaled in picture header, but are inferred to a default value.

In one example, the proposed flag is named as ph_all_intra_flag. The usage of this flag is illustrated as follows.

Descriptor picture_header_rbsp( ) {  non_reference_picture_flag u(1)  ph_all_intra_flag u(1)  gdr_pic_flag u(1) ...  if( partition_constraints_override_enabled_flag ) {   partition_constraints_override_flag ue(v)   if( partition_constraints_override_flag ) {    pic_log2_diff_min_qt_min_cb_intra_slice_luma ue(v)    if (!ph_all_intra_flag){     pic_log2_diff_min_qt_min_cb_inter_slice ue(v)     pic_max_mtt_hierarchy_depth_inter_slice ue(v)    }    pic_max_mtt_hierarchy_depth_intra_slice_luma ue(v)    if( pic_max_mtt_hierarchy_depth_intra_slice_luma != 0 ) {     pic_log2_diff_max_bt_min_qt_intra_slice_luma ue(v)     pic_log2_diff_max_tt_min_qt_intra_slice_luma ue(v)    }    if( pic_max_mtt_hierarchy_depth_inter_slice != 0 &&!ph_all_intra_flag) {     pic_log2_diff_max_bt_min_qt_inter_slice ue(v)     pic_log2_diff_max_tt_min_qt_inter_slice ue(v)    }    if( qtbtt_dual_tree_intra_flag ) {     pic_log2_diff_min_qt_min_cb_intra_slice_chroma ue(v)     pic_max_mtt_hierarchy_depth_intra_slice_chroma ue(v)     if( pic_max_mtt_hierarchy_depth_intra_slice_chroma != 0 ) {      pic_log2_diff_max_bt_min_qt_intra_slice_chroma ue(v)      pic_log2_diff_max_tt_min_qt_intra_slice_chroma ue(v)     }    }   }  }  if( cu_qp_delta_enabled_flag ) {   pic_cu_qp_delta_subdiv_intra_slice ue(v)   if (!ph_all_intra_flag)    pic_cu_qp_delta_subdiv_inter_slice ue(v)  }  if( cu_chroma_qp_offset_enabled_flag ) {   pic_cu_chroma_qp_offset_subdiv_intra_slice ue(v)   if (!ph_all_intra_flag)    pic_cu_chroma_qp_offset_subdiv_inter_slice ue(v)  }  if( sps_temporal_mvp_enabled_flag && !pps_temporal_mvp_enabled_idc &&!ph_all_intra_flag)   pic_temporal_mvp_enabled_flag u(1)  if(!pps_mvd_l1_zero_idc &&!ph_all_intra_flag)   mvd_l1_zero_flag u(1)  if( !pps_six_minus_max_num_merge_cand_plus1 &&!ph_all_intra_flag)   pic_six_minus_max_num_merge_cand ue(v)  if( sps_affine_enabled_flag &&    !pps_five_minus_max_num_subblock_merge_cand_plus1 &&!ph_all_intra_flag)   pic_five_minus_max_num_subblock_merge_cand ue(v)  if( sps_fpel_mmvd_enabled_flag &&!ph_all_intra_flag)   pic_fpel_mmvd_enabled_flag u(1)  if( sps_bdof_dmvr_slice_present_flag &&!ph_all_intra_flag)   pic_disable_bdof_dmvr_flag u(1)  if( sps_triangle_enabled_flag && MaxNumMergeCand >= 2 &&    !pps_max_num_merge_cand_minus_max_num_triangle_cand_minus1 &&!ph_all_intra_flag)   pic_max_num_merge_cand_minus_max_num_triangle_cand ue(v)  if ( sps_ibc_enabled_flag )   pic_six_minus_max_num_ibc_merge_cand ue(v) ...

partition_constraints_override_flag equal to 1 specifies that partition constraint parameters are present in the picture header. partition_constraints_override_flag equal to 0 specifies that partition constraint parameters are not present in the picture header. When not present, the value of partition_constraints_override_flag is inferred to be equal to 0.

pic_log2_diff_min_qt_min_cb_intra_slice_luma specifies the difference between the base 2 logarithm of the minimum size in luma samples of a luma leaf block resulting from quadtree splitting of a CTU and the base 2 logarithm of the minimum coding block size in luma samples for luma CUs in the slices with slice_type equal to 2 (I) associated with the picture header. The value of pic_log2_diff_min_qt_min_cb_intra_slice_luma shall be in the range of 0 to CtbLog2SizeY−MinCbLog2SizeY, inclusive. When not present, the value of pic_log2_diff_min_qt_min_cb_luma is inferred to be equal to sps_log2_diff_min_qt_min_cb_intra_slice_luma.

pic_log2_diff_min_qt_min_cb_inter_slice specifies the difference between the base 2 logarithm of the minimum size in luma samples of a luma leaf block resulting from quadtree splitting of a CTU and the base 2 logarithm of the minimum luma coding block size in luma samples for luma CUs in the slices with slice_type equal to 0 (B) or 1 (P) associated with the picture header. The value of pic_log2_diff_min_qt_min_cb_inter_slice shall be in the range of 0 to CtbLog2SizeY−MinCbLog2SizeY, inclusive. When not present, the value of pic_log2_diff_min_qt_min_cb_luma is inferred to be equal to sps_log2_diff_min_qt_min_cb_inter_slice.

pic_max_mtt_hierarchy_depth_inter_slice specifies the maximum hierarchy depth for coding units resulting from multi-type tree splitting of a quadtree leaf in slices with slice_type equal to 0 (B) or 1 (P) associated with the picture header. The value of pic_max_mtt_hierarchy_depth_inter_slice shall be in the range of 0 to CtbLog2SizeY−MinCbLog2SizeY, inclusive. When not present, the value of pic_max_mtt_hierarchy_depth_inter_slice is inferred to be equal to sps_max_mtt_hierarchy_depth_inter_slice.

pic_max_mtt_hierarchy_depth_intra_slice_luma specifies the maximum hierarchy depth for coding units resulting from multi-type tree splitting of a quadtree leaf in slices with slice_type equal to 2 (I) associated with the picture header. The value of pic_max_mtt_hierarchy_depth_intra_slice_luma shall be in the range of 0 to CtbLog2SizeY−MinCbLog2SizeY, inclusive. When not present, the value of pic_max_mtt_hierarchy_depth_intra_slice_luma is inferred to be equal to sps_max_mtt_hierarchy_depth_intra_slice_luma.

pic_log2_diff_max_bt_min_qt_intra_slice_luma specifies the difference between the base 2 logarithm of the maximum size (width or height) in luma samples of a luma coding block that can be split using a binary split and the minimum size (width or height) in luma samples of a luma leaf block resulting from quadtree splitting of a CTU in slices with slice_type equal to 2 (I) associated with the picture header. The value of pic_log2_diff_max_bt_min_qt_intra_slice_luma shall be in the range of 0 to CtbLog2SizeY−MinQtLog2SizeIntraY, inclusive. When not present, the value of pic_log2_diff_max_bt_min_qt_intra_slice_luma is inferred to be equal to sps_log2_diff_max_bt_min_qt_intra_slice_luma.

pic_log2_diff_max_tt_min_qt_intra_slice_luma specifies the difference between the base 2 logarithm of the maximum size (width or height) in luma samples of a luma coding block that can be split using a ternary split and the minimum size (width or height) in luma samples of a luma leaf block resulting from quadtree splitting of a CTU in slices with slice_type equal to 2 (I) associated with the picture header. The value of pic_log2_diff_max_tt_min_qt_intra_slice_luma shall be in the range of 0 to CtbLog2SizeY−MinQtLog2SizeIntraY, inclusive. When not present, the value of pic_log2_diff_max_tt_min_qt_intra_slice_luma is inferred to be equal to sps_log2_diff_max_tt_min_qt_intra_slice_luma.

pic_log2_diff_max_bt_min_qt_inter_slice specifies the difference between the base 2 logarithm of the maximum size (width or height) in luma samples of a luma coding block that can be split using a binary split and the minimum size (width or height) in luma samples of a luma leaf block resulting from quadtree splitting of a CTU in the slices with slice_type equal to 0 (B) or 1 (P) associated with the picture header. The value of pic_log2_diff_max_bt_min_qt_inter_slice shall be in the range of 0 to CtbLog2SizeY−MinQtLog2SizeInterY, inclusive. When not present, the value of pic_log2_diff_max_bt_min_qt_inter_slice is inferred to be equal to sps_log2_diff_max_bt_min_qt_inter_slice.

pic_log2_diff_max_tt_min_qt_inter_slice specifies the difference between the base 2 logarithm of the maximum size (width or height) in luma samples of a luma coding block that can be split using a ternary split and the minimum size (width or height) in luma samples of a luma leaf block resulting from quadtree splitting of a CTU in slices with slice_type equal to 0 (B) or 1 (P) associated with the picture header. The value of pic_log2_diff_max_tt_min_qt_inter_slice shall be in the range of 0 to CtbLog2SizeY−MinQtLog2SizeInterY, inclusive. When not present, the value of pic_log2_diff_max_tt_min_qt_inter_slice is inferred to be equal to sps_log2_diff_max_tt_min_qt_inter_slice.

pic_log2_diff_min_qt_min_cb_intra_slice_chroma specifies the difference between the base 2 logarithm of the minimum size in luma samples of a chroma leaf block resulting from quadtree splitting of a chroma CTU with treeType equal to DUAL_TREE_CHROMA and the base 2 logarithm of the minimum coding block size in luma samples for chroma CUs with treeType equal to DUAL_TREE_CHROMA in slices with slice_type equal to 2 (I) associated with the picture header. The value of pic_log2_diff_min_qt_min_cb_intra_slice_chroma shall be in the range of 0 to CtbLog2SizeY−MinCbLog2SizeY, inclusive. When not present, the value of pic_log2_diff_min_qt_min_cb_intra_slice_chroma is inferred to be equal to sps_log2_diff_min_qt_min_cb_intra_slice_chroma.

pic_max_mtt_hierarchy_depth_intra_slice_chroma specifies the maximum hierarchy depth for chroma coding units resulting from multi-type tree splitting of a chroma quadtree leaf with treeType equal to DUAL_TREE_CHROMA in slices with slice_type equal to 2 (I) associated with the picture header. The value of pic_max_mtt_hierarchy_depth_intra_slice_chroma shall be in the range of 0 to CtbLog2SizeY−MinCbLog2SizeY, inclusive. When not present, the value of pic_max_mtt_hierarchy_depth_intra_slice_chroma is inferred to be equal to sps_max_mtt_hierarchy_depth_intra_slice_chroma.

pic_log2_diff_max_bt_min_qt_intra_slice_chroma specifies the difference between the base 2 logarithm of the maximum size (width or height) in luma samples of a chroma coding block that can be split using a binary split and the minimum size (width or height) in luma samples of a chroma leaf block resulting from quadtree splitting of a chroma CTU with treeType equal to DUAL_TREE_CHROMA in slices with slice_type equal to 2 (I) associated with the picture header. The value of pic_log2_diff_max_bt_min_qt_intra_slice_chroma shall be in the range of 0 to CtbLog2SizeY−MinQtLog2SizeIntraC, inclusive. When not present, the value of pic_log2_diff_max_bt_min_qt_intra_slice_chroma is inferred to be equal to sps_log2_diff_max_bt_min_qt_intra_slice_chroma.

pic_log2_diff_max_tt_min_qt_intra_slice_chroma specifies the difference between the base 2 logarithm of the maximum size (width or height) in luma samples of a chroma coding block that can be split using a ternary split and the minimum size (width or height) in luma samples of a chroma leaf block resulting from quadtree splitting of a chroma CTU with treeType equal to DUAL_TREE_CHROMA in slices with slice_type equal to 2 (I) associated with the picture header. The value of pic_log2_diff_max_tt_min_qt_intra_slice_chroma shall be in the range of 0 to CtbLog2SizeY−MinQtLog2SizeIntraC, inclusive. When not present, the value of pic_log2_diff_max_tt_min_qt_intra_slice_chroma is inferred to be equal to sps_log2_diff_max_tt_min_qt_intra_slice_chroma

pic_cu_qp_delta_subdiv_intra_slice specifies the maximum cbSubdiv value of coding units in intra slice that convey cu_qp_delta_abs and cu_qp_delta_sign_flag. The value of pic_cu_qp_delta_subdiv_intra_slice shall be in the range of 0 to 2*(CtbLog2SizeY−MinQtLog2SizeIntraY+pic_max_mtt_hierarchy_depth_intra_slice_luma), inclusive.

When not present, the value of pic_cu_qp_delta_subdiv_intra_slice is inferred to be equal to 0.

pic_cu_qp_delta_subdiv_inter_slice specifies the maximum cbSubdiv value of coding units that in inter slice convey cu_qp_delta_abs and cu_qp_delta_sign_flag. The value of pic_cu_qp_delta_subdiv_inter_slice shall be in the range of 0 to 2*(CtbLog2SizeY−MinQtLog2SizeInterY+pic_max_mtt_hierarchy_depth_inter_slice), inclusive.

When not present, the value of pic_cu_qp_delta_subdiv_inter_slice is inferred to be equal to 0.

pic_cu_chroma_qp_offset_subdiv_intra_slice specifies the maximum cbSubdiv value of coding units in intra slice that convey cu_chroma_qp_offset_flag. The value of pic_cu_chroma_qp_offset_subdiv_intra_slice shall be in the range of 0 to 2*(CtbLog2SizeY−MinQtLog2SizeIntraY+pic_max_mtt_hierarchy_depth_intra_slice_luma), inclusive.

When not present, the value of pic_cu_chroma_qp_offset_subdiv_intra_slice is inferred to be equal to 0.

pic_cu_chroma_qp_offset_subdiv_inter_slice specifies the maximum cbSubdiv value of coding units in inter slice that convey cu_chroma_qp_offset_flag. The value of pic_cu_chroma_qp_offset_subdiv_inter_slice shall be in the range of 0 to 2*(CtbLog2SizeY−MinQtLog2SizeInterY+pic_max_mtt_hierarchy_depth_inter_slice), inclusive.

When not present, the value of pic_cu_chroma_qp_offset_subdiv_inter_slice is inferred to be equal to 0.

pic_temporal_mvp_enabled_flag specifies whether temporal motion vector predictors can be used for inter prediction for slices associated with the picture header. If pic_temporal_mvp_enabled_flag is equal to 0, the syntax elements of the slices associated with the picture header shall be constrained such that no temporal motion vector predictor is used in decoding of the slices. Otherwise (pic_temporal_mvp_enabled_flag is equal to 1), temporal motion vector predictors may be used in decoding of the slices associated with the picture header.

When pic_temporal_mvp_enabled_flag is not present, the following applies:

-   -   If sps_temporal_mvp_enabled_flag is equal to 0, the value of         pic_temporal_mvp_enabled_flag is inferred to be equal to 0.     -   Otherwise (sps_temporal_mvp_enabled_flag is equal to 1), the         value of pic_temporal_mvp_enabled_flag is inferred to be equal         to pps_temporal_mvp_enabled_idc−1.

mvd_l1_zero_flag equal to 1 indicates that the mvd_coding(x0, y0, 1) syntax structure is not parsed and MvdL1[x0][y0][compIdx] and MvdL1[x0][y0][cpIdx][compIdx] are set equal to 0 for compIdx=0 . . . 1 and cpIdx=0 . . . 2. mvd_l1_zero_flag equal to 0 indicates that the mvd_coding(x0, y0, 1) syntax structure is parsed. When not present, the value of mvd_l1_zero_flag is inferred to be equal to pps_mvd_l1_zero_idc−1.

pic_six_minus_max_num_merge_cand specifies the maximum number of merging motion vector prediction (MVP) candidates supported in the slices associated with the picture header subtracted from 6. The maximum number of merging MVP candidates, MaxNumMergeCand is derived as follows:

MaxNumMergeCand=6−picsix_minus_max_num_merge_cand  (7-111)

The value of MaxNumMergeCand shall be in the range of 1 to 6, inclusive. When not present, the value of pic_six_minus_max_num_merge_cand is inferred to be equal to pps_six_minus_max_num_merge_cand_plus1−1.

pic_five_minus_max_num_subblock_merge_cand specifies the maximum number of subblock-based merging motion vector prediction (MVP) candidates supported in the slice subtracted from 5.

When pic_five_minus_max_num_subblock_merge_cand is not present, the following applies:

-   -   If sps_affine_enabled_flag is equal to 0, the value of         pic_five_minus_max_num_subblock_merge_cand is inferred to be         equal to 5−(sps_sbtmvp_enabled_flag &&         pic_temporal_mvp_enabled_flag).     -   Otherwise (sps_affine_enabled_flag is equal to 1), the value of         pic_five_minus_max_num_subblock_merge_cand is inferred to be         equal to pps_five_minus_max_num_subblock_merge_cand_plus1−1.

The maximum number of subblock-based merging MVP candidates, MaxNumSubblockMergeCand is derived as follows:

MaxNumSubblockMergeCand=5−pic_five_minus_max_num_subblock_merge_cand  (7-112)

The value of MaxNumSubblockMergeCand shall be in the range of 0 to 5, inclusive.

pic_fpel_mmvd_enabled_flag equal to 1 specifies that merge mode with motion vector difference uses integer sample precision in the slices associated with the picture header. pic_fpel_mmvd_enabled_flag equal to 0 specifies that merge mode with motion vector difference can use fractional sample precision in the slices associated with the picture header. When not present, the value of pic_fpel_mmvd_enabled_flag is inferred to be 0.

pic_disable_bdof_dmvr_flag equal to 1 specifies that neither of bi-directional optical flow inter prediction and decoder motion vector refinement based inter bi-prediction is enabled in the slices associated with the picture header. pic_disable_bdof_dmvr_flag equal to 0 specifies that bi-directional optical flow inter prediction or decoder motion vector refinement based inter bi-prediction may or may not be enabled in the slices associated with the picture header. When not present, the value of pic_disable_bdof_dmvr_flag is inferred to be 0.

pic_max_num_merge_cand_minus_max_num_triangle_cand specifies the maximum number of triangular merge mode candidates supported in the slices associated with the picture header subtracted from MaxNumMergeCand.

When pic_max_num_merge_cand_minus_max_num_triangle_cand is not present, and sps_triangle_enabled_flag is equal to 1 and MaxNumMergeCand greater than or equal to 2, pic_max_num_merge_cand_minus_max_num_triangle_cand is inferred to be equal to pps_max_num_merge_cand_minus_max_num_triangle_cand_plus1−1.

The maximum number of triangular merge mode candidates, MaxNumTriangleMergeCand is derived as follows:

MaxNumTriangleMergeCand=MaxNumMergeCand−pic_max_num_merge_cand_minus_max_num_triangle_cand  (7-113)

When pic_max_num_merge_cand_minus_max_num_triangle_cand is present, the value of MaxNumTriangleMergeCand shall be in the range of 2 to MaxNumMergeCand, inclusive.

When pic_max_num_merge_cand_minus_max_num_triangle_cand is not present, and (sps_triangle_enabled_flag is equal to 0 or MaxNumMergeCand is less than 2), MaxNumTriangleMergeCand is set equal to 0.

When MaxNumTriangleMergeCand is equal to 0, triangle merge mode is not allowed for the slices associated with the picture header.

pic_six_minus_max_num_ibc_merge_cand specifies the maximum number of IBC merging block vector prediction (BVP) candidates supported in the slices associated with the picture header subtracted from 6. The maximum number of IBC merging BVP candidates, MaxNumIbcMergeCand is derived as follows:

MaxNumIbcMergeCand=6−pic_six_minus_max_num_ibc_merge_cand  (7-114)

The value of MaxNumIbcMergeCand shall be in the range of 1 to 6, inclusive.

It should be noted that the ph_all_intra_flag flag can be signaled anywhere before the first place it controlling the inter prediction related syntax element, i.e. pic_log2_diff_min_qt_min_cb_inter_slice. It should be noted that one or more places where ph_all_intra_flag might be removed (i.e. only control a sub-set of syntax elements of embodiments of the current specification). As another example, the usage of this flag is illustrated as follows.

 if(!ph_all_intra_flag) {   if(partition_constraints_override_flag ) {    pic_log2_diff_min_at_min_cb_inter_slice ue(v)    pic_max_mtt_hierarchy_depth_inter_slice ue(v)    if( pic_max_mtt_hierarchy_depth_inter_slice != 0 ) {     pic_log2_diff_max_bt_min_qt_inter_slice ue(v)     pic_log2_diff_max_tt_min_at_inter_slice ue(v)    }   }   if(cu_qp_delta_enabled_flag )    pic_cu_qp_delta_subdiv_inter_slice ue(v)   if(cu_chroma_qp_offset_enabled_flag )    pic_cu_chroma_qp_offset_subdiv_inter_slice ue(v)   if( sps_temporal_mvp_enabled_flag ) {    pic_temporal_mvp_enabled_flag u(1) ...    }   }   if(!pps_mvd_l1_zero_idc) {    mvd_l1_zero_flag u(1)     if(sps_bdof_dmvr_slice_present_flag )     pic_disable_bdof_dmvr_flag u(1)   }  }

In particular, the following methods and embodiments implemented by an encoding device are provided. The encoding device may be video encoder 20 of FIG. 1A, or encoder 20 of FIG. 2.

According to an embodiment 1200 (see FIG. 12), the device determines whether a current picture is I picture at block 1201.

Since I picture contains only intra-predicted block, it is not necessary to signal a syntax element designed for inter prediction in a picture header of a bitstream. Thus, when the current picture is I picture, a syntax element designed for inter prediction is not signaled in the picture header. At block 1203, the device sends the bitstream to a decoding device, where the picture header of the bitstream includes a flag which is used to indicate whether the current picture is I picture. In this situation, the flag indicates that the current picture is I picture. The syntax element designed for inter prediction is not signaled in the picture header. When the current picture is I picture, the syntax element designed for inter prediction is inferred to a default value.

When the current picture is not I picture, i.e., the current picture is P or B picture, the device obtains a syntax element designed for inter prediction at block 1205. As described above, the syntax element designed for inter prediction includes one or more of the following elements: pic_log2_diff_min_qt_min_cb_inter_slice, pic_max_mtt_hierarchy_depth_inter_slice, pic_log2_diff_max_bt_min_qt_inter_slice, pic_log2_diff_max_tt_min_qt_inter_slice, pic_cu_qp_delta_subdiv_inter_slice, pic_cu_chroma_qp_offset_subdiv_inter_slice, pic_temporal_mvp_enabled_flag, mvd_l1_zero_flag, pic_fpel_mmvd_enabled_flag, or pic_disable_bdof_dmvr_flag.

At block 1207, the device sends the bitstream to a decoding device. The picture header of the bitstream includes not only a flag which is used to indicate whether the current picture is I picture, but also the syntax element designed for inter prediction. In this situation, the flag indicates that the current picture is not I picture.

For example, the flag is named as ph_all_intra_flag. The ph_all_intra_flag flag is eligibly signaled anywhere before the first place controlling the syntax element designed for inter prediction. The usage of this flag is illustrated as described above.

The following methods and embodiments implemented by a decoding device are provided. The decoding device may be video decoder 30 of FIG. 1A, or decoder 30 of FIG. 3. According to the embodiment 1300 (see FIG. 13), the device receives a bitstream, and parses the bitstream to obtain a flag from a picture header of the bitstream at block 1301, where the flag indicates whether a current picture is I picture.

For example, the flag is named as ph_all_intra_flag. The ph_all_intra_flag flag is eligibly signaled anywhere before the first place controlling the syntax element designed for inter prediction. The usage of this flag is illustrated as described above.

The device determines whether the current picture is I picture based on the flag at block 1303.

When the current picture is I picture, a syntax element designed for inter prediction is not signaled in the picture header, the syntax element designed for inter prediction is inferred to a default value at block 1305.

When the current picture is not I picture, i.e., the current picture is P or B picture, the device obtains a syntax element designed for inter prediction from the picture header of the bitstream at block 1307. As described above, the syntax element designed for inter prediction includes one or more of the following elements: pic_log2_diff_min_qt_min_cb_inter_slice, pic_max_mtt_hierarchy_depth_inter_slice, pic_log2_diff_max_bt_min_qt_inter_slice, pic_log2_diff_max_tt_min_qt_inter_slice, pic_cu_qp_delta_subdiv_inter_slice, pic_cu_chroma_qp_offset_subdiv_inter_slice, pic_temporal_mvp_enabled_flag, mvd_l1_zero_flag, pic_fpel_mmvd_enabled_flag, or pic_disable_bdof_dmvr_flag.

FIG. 14 illustrates embodiments of a device 1400. The device 1400 may be video encoder 20 of FIG. 1A, or encoder 20 of FIG. 2. The device 1400 can be used to implement the embodiment 1200 and the other embodiments described above.

The device 1400 according to the present disclosure, includes a determining unit 1401, an obtaining unit 1402, and a signaling unit 1403. The determining unit 1401, configured to determine whether a current picture is I picture.

The obtaining unit 1402, configured to obtain a syntax element designed for inter prediction when the current picture is not I picture, i.e., P or B picture. As described above, the syntax element designed for inter prediction includes one or more of the following elements: pic_log2_diff_min_qt_min_cb_inter_slice, pic_max_mtt_hierarchy_depth_inter_slice, pic_log2_diff_max_bt_min_qt_inter_slice, pic_log2_diff_max_tt_min_qt_inter_slice, pic_cu_qp_delta_subdiv_inter_slice, pic_cu_chroma_qp_offset_subdiv_inter_slice, pic_temporal_mvp_enabled_flag, mvd_l1_zero_flag, pic_fpel_mmvd_enabled_flag, or pic_disable_bdof_dmvr_flag.

When the current picture is I picture, the syntax element designed for inter prediction is inferred to a default value.

The signaling unit 1403, configured to send a bitstream to a decoding device, where the picture header of the bitstream includes a flag which is used to indicate whether the current picture is I picture.

The picture header of the bitstream further includes syntax element designed for inter prediction when the current picture is not I picture. Since I picture contains only intra-predicted block, it is not necessary to signal a syntax element designed for inter prediction in a picture header of a bitstream.

For example, the flag is named as ph_all_intra_flag. The ph_all_intra_flag flag is eligibly signaled anywhere before the first place controlling the syntax element designed for inter prediction. The usage of this flag is illustrated as described above.

FIG. 15 illustrates embodiments of a device 1500. The device 1500 may be video decoder 30 of FIG. 1A, or decoder 30 of FIG. 3. The device 1500 can be used to implement the embodiment 1300 and the other embodiments described above.

The device 1500 includes an obtaining unit 1501 and a determining unit 1502. The obtaining unit 1501, configured to parse a bitstream to obtain a flag from a picture header of the bitstream, where the flag indicates whether a current picture is I picture. For example, the flag is named as ph_all_intra_flag.

The determining unit 1502, configured to determine whether the current picture is I picture based on the flag.

The obtaining unit 1501, further configured to obtain a syntax element designed for inter prediction from the picture header when the flag indicates that the current picture is not I picture, i.e., P or B picture. When the current picture is I picture, a syntax element designed for inter prediction is not signaled in the picture header, the syntax element designed for inter prediction is inferred to a default value.

Moreover, the following embodiments are provided herein.

Embodiment 1. A method of coding implemented by a decoding device, comprising:

parsing a bitstream; and

obtaining a flag from a picture header of the bitstream, wherein the flag indicates whether a current picture is an I picture.

Embodiment 2. The method of embodiment 1, wherein when the current picture is I picture, the syntax element designed for inter prediction is inferred to a default value.

Embodiment 3. The method of embodiment 1 or 2, wherein the flag is carried in picture header PBSP syntax.

Embodiment 4. The method of any one of embodiments 1-3, wherein the flag is named as ph_all_intra_flag.

Embodiment 5. The method of embodiment 4, wherein the usage of the flag is as following:

if( partition_constraints_override_enabled_flag ) {  partition_constraints_override_flag  if( partition_constraints_override_flag ) {   pic_log2_diff_min_qt_min_cb_intra_slice_luma   if (!ph_all_intra_flag){    pic_log2_diff_min_qt_min_cb_inter_slice    pic_max_mtt_hierarchy_depth_inter_slice   }   pic_max_mtt_hierarchy_depth_intra_slice_luma   if( pic_max_mtt_hierarchy_depth_intra_slice_luma != 0 ) {    pic_log2_diff_max_bt_min_qt_intra_slice_luma    pic_log2_diff_max_tt_min_qt_intra_slice_luma   }   if( pic_max_mtt_hierarchy_depth_inter_slice != 0 &&!ph_all_intra_flag) {    pic_log2_diff_max_bt_min_qt_inter_slice    pic_log2_diff_max_tt_min_qt_inter_slice   }   if( qtbtt_dual_tree_intra_flag ) {    pic_log2_diff_min_qt_min_cb_intra_slice_chroma    pic_max_mtt_hierarchy_depth_intra_slice_chroma    if( pic_max_mtt_hierarchy_depth_intra_slice_chroma != 0 ) {     pic_log2_diff_max_bt_min_qt_intra_slice_chroma     pic_log2_diff_max_tt_min_qt_intra_slice_chroma    }   }  } }

Embodiment 6. The method of embodiment 4 or 5, wherein the usage of the flag is as following:

if( cu_qp_delta_enabled_flag ) {  pic_cu_qp_delta_subdiv_intra_slice  if (!ph_all_intra_flag)   pic_cu_qp_delta_subdiv_inter_slice }

Embodiment 7. The method of any one of embodiments 4-6, wherein the usage of the flag is as following:

if( cu_chroma_qp_offset_enabled_flag ) {  pic_cu_chroma_qp_offset_subdiv_intra_slice  if (!ph_all_intra_flag)   pic_cu_chroma_qp_offset_subdiv_inter_slice }

Embodiment 8. The method of any one of embodiments 4-7, wherein the usage of the flag is as following:

if( sps_temporal_mvp_enabled_flag && !pps_temporal_mvp_enabled_idc &&!ph_all_intra_flag)  pic_temporal_mvp_enabled_flag if(!pps_mvd_l1_zero_idc &&!ph_all_intra_flag)  mvd_l1_zero_flag if( !pps_six_minus_max_num_merge_cand_plus1 &&!ph_all_intra_flag)  pic_six_minus_max_num_merge_cand if( sps_affine_enabled_flag &&   !pps_five_minus_max_num_subblock_merge_cand_plus1 &&!ph_all_intra_flag)  pic_five_minus_max_num_subblock_merge_cand if( sps_fpel_mmvd_enabled_flag &&!ph_all_intra_flag)  pic_fpel_mmvd_enabled_flag if( sps_bdof_dmvr_slice_present_flag &&!ph_all_intra_flag)  pic_disable_bdof_dmvr_flag if( sps_triangle_enabled_flag && MaxNumMergeCand >= 2 &&   !pps_max_num_merge_cand_minus_max_num_triangle_cand_minus1 &&!ph_all_intra_flag)  pic_max_num_merge_cand_minus_max_num_triangle_cand

Embodiment 9. The method of any one of embodiments 1-8, wherein I picture contains only intra-predicted block, while a P or B picture contain inter-predicted block.

Embodiment 10. A method of coding implemented by an encoding device, comprising:

signaling a flag to a picture header of a bitstream, wherein the flag indicates whether a current picture is an I picture; and

sending the bitstream.

Embodiment 11. The method of embodiment 10, wherein when the current picture is I picture, all syntax elements designed for inter prediction is not signaled in picture header.

Embodiment 12. The method of embodiment 10 or 11, wherein when the current picture is I picture, the syntax element designed for inter prediction is inferred to a default value.

Embodiment 13. The method of any one of embodiments 10-12, wherein the flag is signaled in picture header PBSP syntax.

Embodiment 14. The method of any one of embodiments 10-13, wherein the flag is named as ph_all_intra_flag.

Embodiment 15. The method of embodiment 14, wherein the ph_all_intra_flag flag is eligilbly signaled anywhere before the first place controlling the inter prediction related syntax element.

Embodiment 16. The method of embodiment 14 or 15, wherein the usage of the flag is as following:

if( partition_constraints_override_enabled_flag ) {  partition_constraints_override_flag  if( partition_constraints_override_flag ) {   pic_log2_diff_min_qt_min_cb_intra_slice_luma   if (!ph_all_intra_flag){    pic_log2_diff_min_qt_min_cb_inter_slice    pic_max_mtt_hierarchy_depth_inter_slice   }   pic_max_mtt_hierarchy_depth_intra_slice_luma   if( pic_max_mtt_hierarchy_depth_intra_slice_luma != 0 ) {    pic_log2_diff_max_bt_min_qt_intra_slice_luma    pic_log2_diff_max_tt_min_qt_intra_slice_luma   }   if( pic_max_mtt_hierarchy_depth_inter_slice != 0 &&!ph_all_intra_flag) {    pic_log2_diff_max_bt_min_qt_inter_slice    pic_log2_diff_max_tt_min_qt_inter_slice   }   if( qtbtt_dual_tree_intra_flag ) {    pic_log2_diff_min_qt_min_cb_intra_slice_chroma    pic_max_mtt_hierarchy_depth_intra_slice_chroma    if( pic_max_mtt_hierarchy_depth_intra_slice_chroma != 0 ) {     pic_log2_diff_max_bt_min_qt_intra_slice_chroma     pic_log2_diff_max_tt_min_qt_intra_slice_chroma    }   }  } }

Embodiment 17. The method of any one of embodiments 14-16, wherein the usage of the flag is as following:

if( cu_qp_delta_enabled_flag ) {  pic_cu_qp_delta_subdiv_intra_slice  if (!ph_all_intra_flag)   pic_cu_qp_delta_subdiv_inter_slice }

Embodiment 18. The method of any one of embodiments 14-17, wherein the usage of the flag is as following:

if( cu_chroma_qp_offset_enabled_flag ) {  pic_cu_chroma_qp_offset_subdiv_intra_slice  if (!ph_all_intra_flag)   pic_cu_chroma_qp_offset_subdiv_inter_slice }

Embodiment 19. The method of any one of embodiments 14-18, wherein the usage of the flag is as following:

if( sps_temporal_mvp_enabled_flag && !pps_temporal_mvp_enabled_idc &&!ph_all_intra_flag)  pic_temporal_mvp_enabled_flag if(!pps_mvd_l1_zero_idc &&!ph_all_intra_flag)  mvd_l1_zero_flag if( !pps_six_minus_max_num_merge_cand_plus1 &&!ph_all_intra_flag)  pic_six_minus_max_num_merge_cand if( sps_affine_enabled_flag &&   !pps_five_minus_max_num_subblock_merge_cand_plus1 &&!ph_all_intra_flag)  pic_five_minus_max_num_subblock_merge_cand if( sps_fpel_mmvd_enabled_flag &&!ph_all_intra_flag)  pic_fpel_mmvd_enabled_flag if( sps_bdof_dmvr_slice_present_flag &&!ph_all_intra_flag)  pic_disable_bdof_dmvr_flag if( sps_triangle_enabled_flag && MaxNumMergeCand >= 2 &&   !pps_max_num_merge_cand_minus_max_num_triangle_cand_minus1 &&!ph_all_intra_flag)  pic_max_num_merge_cand_minus_max_num_triangle_cand

As discussed above, by indicating whether the current picture is I picture in the picture header of the bitstream, the syntax element designed for inter prediction is not signaled in the picture header when the current picture is I picture. Thus, the embodiments can simplify signaling picture header for all intra pictures, i.e., I picture. Correspondingly, signaling overhead is reduced.

The term “obtaining” may refer to receiving (e.g. explicitly, as a respective parameter from another entity/device or module within the same device, e.g. for the decoder by parsing a bitstream) and/or deriving (e.g. which may also be referred to as implicitly receiving, e.g. for the decoder by parsing other information/parameters from a bitstream and deriving the respective information or parameter from such other information/parameters).

Following is an explanation of the applications of the encoding method as well as the decoding method as shown in the above-mentioned embodiments, and a system using them.

FIG. 16 is a block diagram showing a content supply system 3100 for realizing content distribution service. This content supply system 3100 includes capture device 3102, terminal device 3106, and optionally includes display 3126. The capture device 3102 communicates with the terminal device 3106 over communication link 3104. The communication link may include the communication channel 13 described above. The communication link 3104 includes but not limited to WIFI, Ethernet, Cable, wireless (3G/4G/5G), USB, or any kind of combination thereof, or the like.

The capture device 3102 generates data, and may encode the data by the encoding method as shown in the above embodiments. Alternatively, the capture device 3102 may distribute the data to a streaming server (not shown in the Figures), and the server encodes the data and transmits the encoded data to the terminal device 3106. The capture device 3102 includes but not limited to camera, smart phone or Pad, computer or laptop, video conference system, PDA, vehicle mounted device, or a combination of any of them, or the like. For example, the capture device 3102 may include the source device 12 as described above. When the data includes video, the video encoder 20 included in the capture device 3102 may actually perform video encoding processing. When the data includes audio (i.e., voice), an audio encoder included in the capture device 3102 may actually perform audio encoding processing. For some practical scenarios, the capture device 3102 distributes the encoded video and audio data by multiplexing them together. For other practical scenarios, for example in the video conference system, the encoded audio data and the encoded video data are not multiplexed. Capture device 3102 distributes the encoded audio data and the encoded video data to the terminal device 3106 separately.

In the content supply system 3100, the terminal device 310 receives and reproduces the encoded data. The terminal device 3106 could be a device with data receiving and recovering capability, such as smart phone or Pad 3108, computer or laptop 3110, network video recorder (NVR)/digital video recorder (DVR) 3112, TV 3114, set top box (STB) 3116, video conference system 3118, video surveillance system 3120, personal digital assistant (PDA) 3122, vehicle mounted device 3124, or a combination of any of them, or the like capable of decoding the above-mentioned encoded data. For example, the terminal device 3106 may include the destination device 14 as described above. When the encoded data includes video, the video decoder 30 included in the terminal device is prioritized to perform video decoding. When the encoded data includes audio, an audio decoder included in the terminal device is prioritized to perform audio decoding processing.

For a terminal device with its display, for example, smart phone or Pad 3108, computer or laptop 3110, network video recorder (NVR)/digital video recorder (DVR) 3112, TV 3114, personal digital assistant (PDA) 3122, or vehicle mounted device 3124, the terminal device can feed the decoded data to its display. For a terminal device equipped with no display, for example, STB 3116, video conference system 3118, or video surveillance system 3120, an external display 3126 is contacted therein to receive and show the decoded data.

When each device in this system performs encoding or decoding, the picture encoding device or the picture decoding device, as shown in the above-mentioned embodiments, can be used.

FIG. 17 is a diagram showing a structure of an example of the terminal device 3106. After the terminal device 3106 receives stream from the capture device 3102, the protocol proceeding unit 3202 analyzes the transmission protocol of the stream. The protocol includes but not limited to Real Time Streaming Protocol (RTSP), Hyper Text Transfer Protocol (HTTP), HTTP Live streaming protocol (HLS), MPEG-DASH, Real-time Transport protocol (RTP), Real Time Messaging Protocol (RTMP), or any kind of combination thereof, or the like.

After the protocol proceeding unit 3202 processes the stream, stream file is generated. The file is outputted to a demultiplexing unit 3204. The demultiplexing unit 3204 can separate the multiplexed data into the encoded audio data and the encoded video data. As described above, for some practical scenarios, for example in the video conference system, the encoded audio data and the encoded video data are not multiplexed. In this situation, the encoded data is transmitted to video decoder 3206 and audio decoder 3208 without through the demultiplexing unit 3204.

Via the demultiplexing processing, video elementary stream (ES), audio ES, and optionally subtitle are generated. The video decoder 3206, which includes the video decoder 30 as explained in the above mentioned embodiments, decodes the video ES by the decoding method as shown in the above-mentioned embodiments to generate video frame, and feeds this data to the synchronous unit 3212. The audio decoder 3208, decodes the audio ES to generate audio frame, and feeds this data to the synchronous unit 3212. Alternatively, the video frame may store in a buffer (not shown in FIG. 21) before feeding it to the synchronous unit 3212. Similarly, the audio frame may store in a buffer (not shown in FIG. 21) before feeding it to the synchronous unit 3212.

The synchronous unit 3212 synchronizes the video frame and the audio frame, and supplies the video/audio to a video/audio display 3214. For example, the synchronous unit 3212 synchronizes the presentation of the video and audio information. Information may code in the syntax using time stamps concerning the presentation of coded audio and visual data and time stamps concerning the delivery of the data stream itself.

If subtitle is included in the stream, the subtitle decoder 3210 decodes the subtitle, and synchronizes it with the video frame and the audio frame, and supplies the video/audio/subtitle to a video/audio/subtitle display 3216.

The present specification is not limited to the above-mentioned system, and either the picture encoding device or the picture decoding device in the above-mentioned embodiments can be incorporated into other system, for example, a car system.

Mathematical Operators

The mathematical operators used in this application are similar to those used in the C programming language. However, the results of integer division and arithmetic shift operations are defined more precisely, and additional operations are defined, such as exponentiation and real-valued division. Numbering and counting conventions generally begin from 0, e.g., “the first” is equivalent to the 0-th, “the second” is equivalent to the 1-th, etc.

Arithmetic Operators

The following arithmetic operators are defined as follows:

-   -   + Addition     -   − Subtraction (as a two-argument operator) or negation (as a         unary prefix operator)     -   * Multiplication, including matrix multiplication     -   x^(y) Exponentiation. Specifies x to the power of y. In other         contexts, such notation is used for superscripting not intended         for interpretation as exponentiation.     -   / Integer division with truncation of the result toward zero.         For example, 7/4 and −7/−4 are truncated to 1 and −7/4 and 7/−4         are truncated to −1.     -   ÷ Used to denote division in mathematical equations where no         truncation or rounding is intended.

$\frac{x}{y}$

-   -    Used to denote division in mathematical equations where no         truncation or rounding is intended.

$\sum\limits_{i = x}^{y}{f(i)}$

-   -    The summation of f(i) with i taking all integer values from x         up to and including y.     -   Modulus. Remainder of x divided by y, defined only for integers         x and y with x>=0 x % y and y>0.

Logical Operators

The following logical operators are defined as follows:

-   -   x && y Boolean logical “and” of x and y     -   x∥y Boolean logical “or” of x and y     -   ! Boolean logical “not”     -   x ? y : z If x is TRUE or not equal to 0, evaluates to the value         of y; otherwise, evaluates to the value of z.

Relational Operators

The following relational operators are defined as follows:

-   -   > Greater than     -   >= Greater than or equal to     -   < Less than     -   <= Less than or equal to     -   == Equal to     -   != Not equal to

When a relational operator is applied to a syntax element or variable that has been assigned the value “na” (not applicable), the value “na” is treated as a distinct value for the syntax element or variable. The value “na” is considered not to be equal to any other value.

Bit-Wise Operators

The following bit-wise operators are defined as follows:

-   -   & Bit-wise “and”. When operating on integer arguments, operates         on a two's complement representation of the integer value. When         operating on a binary argument that contains fewer bits than         another argument, the shorter argument is extended by adding         more significant bits equal to 0.     -   | Bit-wise “or”. When operating on integer arguments, operates         on a two's complement representation of the integer value. When         operating on a binary argument that contains fewer bits than         another argument, the shorter argument is extended by adding         more significant bits equal to 0.     -   {circumflex over ( )} A Bit-wise “exclusive or”. When operating         on integer arguments, operates on a two's complement         representation of the integer value. When operating on a binary         argument that contains fewer bits than another argument, the         shorter argument is extended by adding more significant bits         equal to 0.     -   x>>y Arithmetic right shift of a two's complement integer         representation of x by y binary digits. This function is defined         only for non-negative integer values of y. Bits shifted into the         most significant bits (MSBs) as a result of the right shift have         a value equal to the MSB of x prior to the shift operation.     -   x<<y Arithmetic left shift of a two's complement integer         representation of x by y binary digits. This function is defined         only for non-negative integer values of y. Bits shifted into the         least significant bits (LSBs) as a result of the left shift have         a value equal to 0.

Assignment Operators

The following arithmetic operators are defined as follows:

-   -   = Assignment operator     -   ++ Increment, i.e., x++ is equivalent to x=x+1; when used in an         array index, evaluates to the value of the variable prior to the         increment operation.     -   −− Decrement, i.e., x−− is equivalent to x=x−1; when used in an         array index, evaluates to the value of the variable prior to the         decrement operation.     -   += Increment by amount specified, i.e., x+=3 is equivalent to         x=x+3, and x+=(−3) is equivalent to x=x+(−3).     -   −= Decrement by amount specified, i.e., x−=3 is equivalent to         x=x−3, and x−=(−3) is equivalent to x=x−(−3).

Range Notation

The following notation is used to specify a range of values:

-   -   x=y . . . z x takes on integer values starting from y to z,         inclusive, with x, y, and z being integer numbers and z being         greater than y.

Mathematical Functions

The following mathematical functions are defined:

${{Abs}(x)} = \left\{ \begin{matrix} {x;} & {x>=0} \\ {{- x};} & {x < 0} \end{matrix} \right.$

-   -   Asin(x) the trigonometric inverse sine function, operating on an         argument x that is in the range of −1.0 to 1.0, inclusive, with         an output value in the range of −π÷2 to π÷2, inclusive, in units         of radians     -   Atan(x) the trigonometric inverse tangent function, operating on         an argument x, with an output value in the range of −π÷2 to π÷2,         inclusive, in units of radians

${A\;\tan\; 2\left( {y,x} \right)} = \left\{ \begin{matrix} {{A\;{\tan\ \left( \frac{y}{x} \right)}};} & {x > 0} \\ {{{A\;{\tan\ \left( \frac{y}{x} \right)}} + \pi}\ ;} & {{x < 0}\ \&\&\ {y>=0}} \\ {{{A\;{\tan\ \left( \frac{y}{x} \right)}} - \pi}\ ;} & {{x < 0}\ \&\&\ {y < 0}} \\ {{+ \frac{\pi}{2}};} & {{{x==0}\ \&\&\ {y >}} = 0} \\ {{- \frac{\pi}{2}};} & {otherwise} \end{matrix} \right.$

-   -   Ceil(x) the smallest integer greater than or equal to x.

Clip 1_(Y)(x) = Clip 3(0, (1 ⪡ BitDepth_(Y)) − 1, x) Clip 1_(C)(x) = Clip 3(0, (1 ⪡ BitDepth_(C)) − 1, x) ${{Clip}\; 3\left( {x,y,z} \right)} = \left\{ \begin{matrix} {x;} & {z < x} \\ {y;} & {z > y} \\ {z;} & {otherwise} \end{matrix} \right.$

-   -   Cos(x) the trigonometric cosine function operating on an         argument x in units of radians     -   Floor(x) the largest integer less than or equal to x.

${{GetCurrMsb}\left( {a,b,c,d} \right)} = \left\{ \begin{matrix} {{c + d};} & {{b - a}>={d/2}} \\ {{c - d};} & {{a - b} > {d/2}} \\ {c;} & {otherwise} \end{matrix} \right.$

-   -   Ln(x) the natural logarithm of x (the base-e logarithm, where e         is the natural logarithm base constant 2.718 281 828 . . . ).     -   Log 2(x) the base-2 logarithm of x.     -   Log 10(x) the base-10 logarithm of x.

${{Min}\left( {x,y} \right)} = \left\{ {{\begin{matrix} {x;} & {x<=y} \\ {y;} & {x > y} \end{matrix}{{Max}\left( {x,y} \right)}} = \left\{ {{\begin{matrix} {x;} & {x>=y} \\ {y;} & {x < y} \end{matrix}{{Round}(x)}} = {{{Sign}\mspace{11mu}(x)*{Floor}\mspace{11mu}\left( {{{Abs}(x)} + 0.5} \right){Sign}\;(x)} = \left\{ \begin{matrix} {1;} & {x > 0} \\ {0;} & {x==0} \\ {{- 1};} & {x < 0} \end{matrix} \right.}} \right.} \right.$

-   -   Sin(x) the trigonometric sine function operating on an argument         x in units of radians     -   Sqrt(x)=√{square root over (x)}     -   Swap(x,y)=(y,x)     -   Tan(x) the trigonometric tangent function operating on an         argument x in units of radians

Order of Operation Precedence

When an order of precedence in an expression is not indicated explicitly by use of parentheses, the following rules apply:

-   -   Operations of a higher precedence are evaluated before any         operation of a lower precedence.     -   Operations of the same precedence are evaluated sequentially         from left to right.

The table below specifies the precedence of operations from highest to lowest; a higher position in the table indicates a higher precedence.

For those operators that are also used in the C programming language, the order of precedence used in this Specification is the same as used in the C programming language.

TABLE Operation precedence from highest (at top of table) to lowest (at bottom of table) operations (with operands x, y, and z) ″x++″, ″x− −″ ″!x″, ″−x″ (as a unary prefix operator) x^(y) ″x * y″, ″x/y″, ″x ÷ y″, ″ x/y″, ″x % y″ ″x + y″, ″x − y″ (as a two-argument operator), $\;^{''}{\underset{i = x}{\sum\limits^{y}}{f(i)}^{''}}$ ″x << y″, ″x >> y″ ″x < y″, ″x <= y″, ″x > y″, ″x >= y″ ″x = = y″, ″x != y″ ″x & y″ ″x | y″ ″x && y″ ″x ∥ y″ ″x ? y : z″ ″x . . . y″ ″x = y″, ″x += y″, ″x −= y″

Text Description of Logical Operations

In the text, a statement of logical operations as would be described mathematically in the following form:

if( condition 0 )  statement 0 else if( condition 1 )  statement 1 ... else /* informative remark on remaining condition */  statement n

may be described in the following manner:

. . . as follows / . . . the following applies:

-   -   If condition 0, statement 0     -   Otherwise, if condition 1, statement 1     -   . . .     -   Otherwise (informative remark on remaining condition), statement         n

Each “If . . . Otherwise, if . . . Otherwise, . . . ” statement in the text is introduced with “ . . . as follows” or “ . . . the following applies” immediately followed by “If . . . ”. The last condition of the “If . . . Otherwise, if . . . Otherwise, . . . ” is always an “Otherwise, . . . ”. Interleaved “If . . . Otherwise, if . . . Otherwise, . . . ” statements can be identified by matching “ . . . as follows” or “ . . . the following applies” with the ending “Otherwise, . . . ”.

In the text, a statement of logical operations as would be described mathematically in the following form:

if( condition 0a && condition 0b )  statement 0 else if( condition 1a | | condition 1b )  statement 1 ... else  statement n

may be described in the following manner:

. . . as follows / . . . the following applies:

-   -   If all of the following conditions are true, statement 0:         -   condition 0a         -   condition 0b     -   Otherwise, if one or more of the following conditions are true,         statement 1:         -   condition 1a         -   condition 1b     -   . . .     -   Otherwise, statement n

In the text, a statement of logical operations as would be described mathematically in the following form:

-   -   if(condition 0)         -   statement 0     -   if(condition 1)         -   statement 1

may be described in the following manner:

-   -   When condition 0, statement 0     -   When condition 1, statement 1

Although embodiments of the specification have been primarily described based on video coding, it should be noted that embodiments of the coding system 10, encoder 20 and decoder 30 (and correspondingly the system 10) and the other embodiments described herein may also be configured for still picture processing or coding, i.e. the processing or coding of an individual picture independent of any preceding or consecutive picture as in video coding. In general only inter-prediction units 244 (encoder) and 344 (decoder) may not be available in case the picture processing coding is limited to a single picture 17. All other functionalities (also referred to as tools or technologies) of the video encoder 20 and video decoder 30 may equally be used for still picture processing, e.g. residual calculation 204/304, transform 206, quantization 208, inverse quantization 210/310, (inverse) transform 212/312, partitioning 262/362, intra-prediction 254/354, and/or loop filtering 220, 320, and entropy coding 270 and entropy decoding 304.

Embodiments, e.g. of the encoder 20 and the decoder 30, and functions described herein, e.g. with reference to the encoder 20 and the decoder 30, may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium or transmitted over communication media as one or more instructions or code and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to a tangible medium such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another, e.g., according to a communication protocol. In this manner, computer-readable media generally may correspond to (1) tangible computer-readable storage media which is non-transitory or (2) a communication medium such as a signal or carrier wave. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code and/or data structures for implementation of the techniques described in this disclosure. A computer program product may include a computer-readable medium.

By way of example, and not limiting, such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transitory media, but are instead directed to non-transitory, tangible storage media. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor,” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. In addition, in some aspects, the functionality described herein may be provided within dedicated hardware and/or software modules configured for encoding and decoding, or incorporated in a combined codec. Also, the techniques could be fully implemented in one or more circuits or logic elements.

The techniques of this disclosure may be implemented in a wide variety of devices or apparatuses, including a wireless handset, an integrated circuit (IC) or a set of ICs (e.g., a chip set). Various components, modules, or units are described in this disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but do not necessarily require realization by different hardware units. Rather, as described above, various units may be combined in a codec hardware unit or provided by a collection of interoperative hardware units, including one or more processors as described above, in conjunction with suitable software and/or firmware. 

What is claimed is:
 1. A method of coding implemented by a decoding device, comprising: parsing a bitstream to obtain a flag from a picture header of the bitstream, wherein the flag indicates whether a current picture is I picture; and when the flag indicates that the current picture is I picture, inferring a syntax element used for inter prediction to a default value; or when the flag indicates that the current picture is P or B picture, obtaining a syntax element used for inter prediction from the picture header.
 2. The method of claim 1, wherein the syntax element used for inter prediction includes pic_log2_diff_min_qt_min_cb_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_log2_diff_min_qt_min_cb_inter_slice specifies a difference between base 2 logarithm of a minimum size in luma samples of a luma leaf block resulting from quadtree splitting of a coding tree unit (CTU) and base 2 logarithm of a minimum luma coding block size in luma samples for luma coding units (CUs) in slices with P or B picture associated with the picture header; or wherein when the flag indicates that the current picture is I picture, a value of pic_log2_diff_min_qt_min_cb_luma is inferred to be equal to sps_log2_diff_min_qt_min_cb_inter_slice.
 3. The method of claim 1, wherein the syntax element used for inter prediction further includes pic_max_mtt_hierarchy_depth_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_max_mtt_hierarchy_depth_inter_slice specifies a maximum hierarchy depth for coding units resulting from multi-type tree splitting of a quadtree leaf in slices; or wherein when the flag indicates that the current picture is I picture, the value of pic_max_mtt_hierarchy_depth_inter_slice is inferred to be equal to sps_max_mtt_hierarchy_depth_inter_slice.
 4. The method of claim 3, wherein when pic_max_mtt_hierarchy_depth_inter_slice is not equal to 0, the syntax element used for inter prediction further includes pic_log2_diff_max_bt_min_qt_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_log2_diff_max_bt_min_qt_inter_slice specifies a difference between base 2 logarithm of a maximum size (width or height) in luma samples of a luma coding block that can be split using a binary split and base 2 logarithm of a minimum size (width or height) in luma samples of a luma leaf block resulting from quadtree splitting of a CTU in the slices; or wherein when the flag indicates that the current picture is I picture, a value of pic_log2_diff_max_bt_min_qt_inter_slice is inferred to be equal to sps_log2_diff_max_bt_min_qt_inter_slice.
 5. The method of claim 3, wherein when pic_max_mtt_hierarchy_depth_inter_slice is not equal to 0, the syntax element used for inter prediction further includes pic_log2_diff_max_tt_min_qt_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_log2_diff_max_tt_min_qt_inter_slice specifies a difference between base 2 logarithm of a maximum size (width or height) in luma samples of a luma coding block that can be split using a ternary split and base 2 logarithm of a minimum size (width or height) in luma samples of a luma leaf block resulting from quadtree splitting of a CTU in slices; or wherein when the flag indicates that the current picture is I picture, a value of pic_log2_diff_max_tt_min_qt_inter_slice is inferred to be equal to sps_log2_diff_max_tt_min_qt_inter_slice.
 6. The method of claim 1, wherein the syntax element used for inter prediction includes pic_cu_qp_delta_subdiv_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_cu_qp_delta_subdiv_inter_slice specifies a maximum cbSubdiv value of coding units that in inter slice convey cu_qp_delta_abs and cu_qp_delta_sign_flag; or wherein when the flag indicates that the current picture is I picture, a value of pic_cu_qp_delta_subdiv_inter_slice is inferred to be equal to
 0. 7. The method of claim 1, wherein the syntax element used for inter prediction includes pic_cu_chroma_qp_offset_subdiv_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_cu_chroma_qp_offset_subdiv_inter_slice specifies a maximum cbSubdiv value of coding units in inter slice that convey cu_chroma_qp_offset_flag; or wherein when the flag indicates that the current picture is I picture, a value of pic_cu_chroma_qp_offset_subdiv_inter_slice is inferred to be equal to
 0. 8. The method of claim 1, wherein the flag is carried in picture header PBSP syntax.
 9. A decoder, comprising: at least one processor; and at least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor to cause the processor to: parse a bitstream to obtain a flag from a picture header of the bitstream, wherein the flag indicates whether a current picture is I picture; determine whether the current picture is I picture based on the flag; and obtain a syntax element used for inter prediction from the picture header when the flag indicates that the current picture is P or B picture.
 10. The decoder of claim 9, wherein when the flag indicates that the current picture is I picture, the syntax element used for inter prediction is inferred to a default value.
 11. The decoder of claim 10, wherein the syntax element used for inter prediction includes pic_log2_diff_min_qt_min_cb_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_log2_diff_min_qt_min_cb_inter_slice specifies a difference between base 2 logarithm of a minimum size in luma samples of a luma leaf block resulting from quadtree splitting of a coding tree unit (CTU) and base 2 logarithm of a minimum luma coding block size in luma samples for luma coding units (CUs) in slices with P or B picture associated with the picture header; or wherein when the flag indicates that the current picture is I picture, a value of pic_log2_diff_min_qt_min_cb_luma is inferred to be equal to sps_log2_diff_min_qt_min_cb_inter_slice.
 12. The decoder of claim 10, wherein the syntax element used for inter prediction includes pic_max_mtt_hierarchy_depth_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_max_mtt_hierarchy_depth_inter_slice specifies a maximum hierarchy depth for coding units resulting from multi-type tree splitting of a quadtree leaf in slices; or wherein when the flag indicates that the current picture is I picture, a value of pic_max_mtt_hierarchy_depth_inter_slice is inferred to be equal to sps_max_mtt_hierarchy_depth_inter_slice.
 13. The decoder of claim 12, wherein when pic_max_mtt_hierarchy_depth_inter_slice is not equal to 0, the syntax element used for inter prediction further includes pic_log2_diff_max_bt_min_qt_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_log2_diff_max_bt_min_qt_inter_slice specifies a difference between base 2 logarithm of a maximum size (width or height) in luma samples of a luma coding block that can be split using a binary split and base 2 logarithm of a minimum size (width or height) in luma samples of a luma leaf block resulting from quadtree splitting of a CTU in the slices; or wherein when the flag indicates that the current picture is I picture, a value of pic_log2_diff_max_bt_min_qt_inter_slice is inferred to be equal to sps_log2_diff_max_bt_min_qt_inter_slice.
 14. The decoder of claim 12, wherein when pic_max_mtt_hierarchy_depth_inter_slice is not equal to 0, the syntax element used for inter prediction further includes pic_log2_diff_max_tt_min_qt_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_log2_diff_max_tt_min_qt_inter_slice specifies a difference between base 2 logarithm of a maximum size (width or height) in luma samples of a luma coding block that can be split using a ternary split and base 2 logarithm of a minimum size (width or height) in luma samples of a luma leaf block resulting from quadtree splitting of a CTU in slices; or wherein when the flag indicates that the current picture is I picture, a value of pic_log2_diff_max_tt_min_qt_inter_slice is inferred to be equal to sps_log2_diff_max_tt_min_qt_inter_slice.
 15. The decoder of claim 9, wherein the flag is carried in picture header PBSP syntax.
 16. A non-transitory computer readable medium comprising computer executable instructions when executed by a processor, cause a video coding device to: parse a bitstream to obtain a flag from a picture header of the bitstream, wherein the flag indicates whether a current picture is I picture; determine whether the current picture is I picture based on the flag; and obtain a syntax element used for inter prediction from the picture header when the flag indicates that the current picture is P or B picture.
 17. The non-transitory computer readable medium of claim 16, wherein when the flag indicates that the current picture is I picture, the syntax element used for inter prediction is inferred to a default value.
 18. The non-transitory computer readable medium of claim 16, wherein the syntax element used for inter prediction includes pic_log2_diff_min_qt_min_cb_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_log2_diff_min_qt_min_cb_inter_slice specifies a difference between base 2 logarithm of a minimum size in luma samples of a luma leaf block resulting from quadtree splitting of a coding tree unit (CTU) and base 2 logarithm of a minimum luma coding block size in luma samples for luma coding units (CUs) in slices with P or B picture associated with the picture header; or wherein when the flag indicates that the current picture is I picture, a value of pic_log2_diff_min_qt_min_cb_luma is inferred to be equal to sps_log2_diff_min_qt_min_cb_inter_slice.
 19. The non-transitory computer readable medium of claim 16, wherein the syntax element used for inter prediction includes pic_max_mtt_hierarchy_depth_inter_slice, wherein when the flag indicates that the current picture is P or B picture, pic_max_mtt_hierarchy_depth_inter_slice specifies a maximum hierarchy depth for coding units resulting from multi-type tree splitting of a quadtree leaf in slices; or wherein when the flag indicates that the current picture is I picture, a value of pic_max_mtt_hierarchy_depth_inter_slice is inferred to be equal to sps_max_mtt_hierarchy_depth_inter_slice.
 20. The non-transitory computer readable medium of claim 16, wherein the flag is carried in picture header PBSP syntax. 